opensearch-project / opensearch-project/data-prepper

Process Termination on Pipeline Shutdown

Open
#2,595 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
At present we are testing data-prepper in a k8s environment, for a new piece of work we are looking at.

The current issue we are having is a heap issue (I will raise another issue for this), that when we run out of heap space all our pipelines shutdown , which is fine. However we would like the option that once the pipelines have shutdown the data-prepper process is terminated, which is not happening at present, which means our pods continue to run although they process nothing.

Describe the solution you'd like
On pipeline shutdown for the option to kill the process, and in turn for the pod to be restarted

Describe alternatives you've considered (Optional)
We will investigate health check's but this is a belt and braces type thing

Additional context
This would be an extension to this PR (I think) https://github.com/opensearch-project/data-prepper/pull/2540/files

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the pipeline-shutdown changes in PR 2540 and trace how shutdown currently affects the Data Prepper process and Kubernetes pod lifecycle. Define how an opt-in process-termination behavior should be configured and verify that, when enabled, shutting down the pipelines causes the process to exit so the pod can restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kubernetes
Domain
backend, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.