[
https://issues.apache.org/jira/browse/FLINK-16333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16333:
-----------------------------------
Labels: auto-deprioritized-critical stale-major (was:
auto-deprioritized-critical)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> After exiting from the command line client, the process still exists
> --------------------------------------------------------------------
>
> Key: FLINK-16333
> URL: https://issues.apache.org/jira/browse/FLINK-16333
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Affects Versions: 1.10.0
> Environment: JDK 8
> Flink 1.10
> Reporter: jinxin
> Priority: Major
> Labels: auto-deprioritized-critical, stale-major
> Attachments: 微信图片_20200228190743.png, 微信图片_20200228190935.png
>
>
> After exiting from flink scala shell, the process still exists. Then I tried
> to kill him with kill -9 PID, but it still didn't work. Process still exists.
> Similar problems also appear in SQL client.Fortunately, kill-9 takes effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
