[
https://issues.apache.org/jira/browse/FLINK-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17034:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Execute the container CMD under TINI for better hygiene
> --------------------------------------------------------
>
> Key: FLINK-17034
> URL: https://issues.apache.org/jira/browse/FLINK-17034
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes, flink-docker
> Reporter: Canbin Zheng
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> The container of the JM or TMs is running in the shell form and it could not
> receive the *TERM* signal when the pod is deleted. Some of the problems are
> as follows:
> * The JM and the TMs could have no chance of cleanup, I used to create
> FLINK-15843[4] for tracking this problem.
> * The pod could take a long time(up to 40 seconds) to be deleted after the
> K8s API Server receives the deletion request.
> The discussion could refer to
> [http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-111-Docker-image-unification-td38444i20.html]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
