[jira] [Closed] (FLINK-32461) manage union operator state increase very large in Jobmanager

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn closed FLINK-32461. Release Note: it's a usage problem Resolution: Fixed > manage union operator state increase very large in J

[jira] (FLINK-32461) manage union operator state increase very large in Jobmanager

[ https://issues.apache.org/jira/browse/FLINK-32461 ] wgcn deleted comment on FLINK-32461: -- was (Author: 1026688210): the issue This issue is related to https://issues.apache.org/jira/browse/FLINK-21436 . Can we reopen it and continue the discussion?

[jira] [Commented] (FLINK-32461) manage union operator state increase very large in Jobmanager

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738928#comment-17738928 ] wgcn commented on FLINK-32461: -- the issue This issue is related to https://issues.apache.o

[jira] [Updated] (FLINK-32461) manage union operator state increase very large in Jobmanager

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Summary: manage union operator state increase very large in Jobmanager (was: manage operator state increase v

[jira] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461 ] wgcn deleted comment on FLINK-32461: -- was (Author: 1026688210): >> This issue doesn't usually occur, but it happens during busy nights when the machines are more active. The "manage operator

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Description: This issue doesn't usually occur, but it happens during busy nights when the machines are more act

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Description: This issue doesn't usually occur, but it happens during busy nights when the machines are more act

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Description: This issue doesn't usually occur, but it happens during busy nights when the machines are more act

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Attachment: image-2023-06-28-16-24-11-538.png Description: This issue doesn't usually occur, but it happen

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Attachment: (was: image-2023-06-28-15-57-52-615.png) > manage operator state increase very large >

[jira] [Commented] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738010#comment-17738010 ] wgcn commented on FLINK-32461: -- >> This issue doesn't usually occur, but it happens d

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Attachment: screenshot-1.png > manage operator state increase very large >

[jira] [Updated] (FLINK-32461) manage operator state increase very large

[ https://issues.apache.org/jira/browse/FLINK-32461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32461: - Description: !screenshot-1.png! This issue doesn't usually occur, but it happens during busy nights when the

[jira] [Created] (FLINK-32461) manage operator state increase very large

wgcn created FLINK-32461: Summary: manage operator state increase very large Key: FLINK-32461 URL: https://issues.apache.org/jira/browse/FLINK-32461 Project: Flink Issue Type: Bug Affects Versio

[jira] [Commented] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733968#comment-17733968 ] wgcn commented on FLINK-32319: -- It work after I increase "taskmanager.memory.network"，but I

[jira] [Comment Edited] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732799#comment-17732799 ] wgcn edited comment on FLINK-32319 at 6/14/23 11:26 PM: Hi~[~Wen

[jira] [Commented] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732799#comment-17732799 ] wgcn commented on FLINK-32319: -- Hi~[~Wencong Liu],I Increased taskmanager.network.request-b

[jira] [Commented] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731827#comment-17731827 ] wgcn commented on FLINK-32319: -- hi~ [~Wencong Liu] thanks for your response, I will try t

[jira] [Updated] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32319: - Environment: centos 7. jdk 8. flink1.17.1 application mode on yarn flink configuration : ``` $internal.appli

[jira] [Updated] (FLINK-32319) flink can't the partition of network after restart

[ https://issues.apache.org/jira/browse/FLINK-32319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-32319: - Attachment: image-2023-06-13-07-14-48-958.png Component/s: Runtime / Network Affects Version

[jira] [Created] (FLINK-32319) flink can't the partition of network after restart

wgcn created FLINK-32319: Summary: flink can't the partition of network after restart Key: FLINK-32319 URL: https://issues.apache.org/jira/browse/FLINK-32319 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-30720) KafkaChangelogTableITCase.testKafkaDebeziumChangelogSource failed due to a topic already exist when creating it

[ https://issues.apache.org/jira/browse/FLINK-30720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693657#comment-17693657 ] wgcn commented on FLINK-30720: -- Hi [~mapohl] ,does this Exception occur in every test? C

[jira] [Comment Edited] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232000#comment-17232000 ] wgcn edited comment on FLINK-20138 at 11/14/20, 12:17 PM: -- [~tr

[jira] [Comment Edited] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232000#comment-17232000 ] wgcn edited comment on FLINK-20138 at 11/14/20, 12:13 PM: -- [~tr

[jira] [Comment Edited] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232000#comment-17232000 ] wgcn edited comment on FLINK-20138 at 11/14/20, 12:11 PM: -- [~tr

[jira] [Commented] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232000#comment-17232000 ] wgcn commented on FLINK-20138: -- [~trohrmann] , the log 'Connecting to ResourceManager x

[jira] [Commented] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231966#comment-17231966 ] wgcn commented on FLINK-20138: -- [~trohrmann] I upload the resource_manager_lock at the att

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Attachment: zk_resource_address_info.png > Flink Job can not recover due to timeout of requiring slots when fli

[jira] [Closed] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn closed FLINK-18715. Resolution: Won't Do > add cpu usage metric of jobmanager/taskmanager > ---

[jira] [Commented] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231130#comment-17231130 ] wgcn commented on FLINK-20138: -- hi~ [~trohrmann] please have a look at this issue > Flink

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Description: our flink jobs run on Yarn Perjob Mode. We stoped some nodemanger machines ,and AMs of the m

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Description: our flink jobs run on Yarn Perjob Mode. We stoped some nodemanger machines ,and AMs of the m

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Description: our flink jobs run on Yarn Perjob Mode. We stoped some nodemanger machines ,and AMs of the m

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Attachment: jobmanager.log > Flink Job can not recover due to timeout of requiring slots when flink > jobmanag

[jira] [Updated] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

[ https://issues.apache.org/jira/browse/FLINK-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-20138: - Attachment: 2820F7EE-85F9-441D-95D5-8163FB6267DF.png > Flink Job can not recover due to timeout of requiring sl

[jira] [Created] (FLINK-20138) Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted

wgcn created FLINK-20138: Summary: Flink Job can not recover due to timeout of requiring slots when flink jobmanager restarted Key: FLINK-20138 URL: https://issues.apache.org/jira/browse/FLINK-20138 Project:

[jira] [Commented] (FLINK-19943) Support sink parallelism configuration to ElasticSearch connector

[ https://issues.apache.org/jira/browse/FLINK-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225333#comment-17225333 ] wgcn commented on FLINK-19943: -- I want to have a try .Please assign it to me [~lzljs36203

[jira] [Commented] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166396#comment-17166396 ] wgcn commented on FLINK-18715: -- [~trohrmann] it's not suitable for the deployment scenario

[jira] [Comment Edited] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166353#comment-17166353 ] wgcn edited comment on FLINK-18715 at 7/28/20, 11:30 AM: - [~ches

[jira] [Comment Edited] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166353#comment-17166353 ] wgcn edited comment on FLINK-18715 at 7/28/20, 11:27 AM: - [~ches

[jira] [Commented] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166353#comment-17166353 ] wgcn commented on FLINK-18715: -- [~chesnay] it indeed has a lot of system resources , we

[jira] [Commented] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166213#comment-17166213 ] wgcn commented on FLINK-18715: -- Thanks for your concern [~trohrmann]. We use yarn as reso

[jira] [Updated] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-18715: - Description: flink process add cpu usage metric, user can determine that their job is io bound /cpu bound

[jira] [Updated] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

[ https://issues.apache.org/jira/browse/FLINK-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-18715: - Description: flink process add cpu usage metric, user can determine that their job is io bound /cpu bound

[jira] [Created] (FLINK-18715) add cpu usage metric of jobmanager/taskmanager

wgcn created FLINK-18715: Summary: add cpu usage metric of jobmanager/taskmanager Key: FLINK-18715 URL: https://issues.apache.org/jira/browse/FLINK-18715 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-16360) connector on hive 2.0.1 don't support type conversion from STRING to VARCHAR

wgcn created FLINK-16360: Summary: connector on hive 2.0.1 don't support type conversion from STRING to VARCHAR Key: FLINK-16360 URL: https://issues.apache.org/jira/browse/FLINK-16360 Project: Flink

[jira] [Commented] (FLINK-15350) develop JDBC catalogs to connect to relational databases

[ https://issues.apache.org/jira/browse/FLINK-15350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018800#comment-17018800 ] wgcn commented on FLINK-15350: -- Hi~ [~phoenixjiangnan] , I wanna know which scene JDBC

[jira] [Commented] (FLINK-15625) flink sql multiple statements syntatic validation supports

[ https://issues.apache.org/jira/browse/FLINK-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018773#comment-17018773 ] wgcn commented on FLINK-15625: -- [~jark]thks for your reply . i will be concern about [Fl

[jira] [Commented] (FLINK-15625) flink sql multiple statements syntatic validation supports

[ https://issues.apache.org/jira/browse/FLINK-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017909#comment-17017909 ] wgcn commented on FLINK-15625: -- hi , [~lzljs3620320]we can support a sql text which co

[jira] [Commented] (FLINK-15625) flink sql multiple statements syntatic validation supports

[ https://issues.apache.org/jira/browse/FLINK-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017738#comment-17017738 ] wgcn commented on FLINK-15625: -- it's indeed a good improvement , and it's seem to not com

[jira] [Closed] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn closed FLINK-12728. Resolution: Resolved *in  core-site.xml* hadoop.proxyuser.yarn.hosts * hadoop.proxyuser.yarn.groups

[jira] [Commented] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888705#comment-16888705 ] wgcn commented on FLINK-12728: -- hi Tao Yang,Andrey Zagrebin   it's does work by  setting y

[jira] [Commented] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881895#comment-16881895 ] wgcn commented on FLINK-12728: -- hi Andrey Zagrebin  The issue did happen again  after yarn

[jira] [Updated] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-12728: - Description:     job can't restart when flink  job  has been running for a long time and then taskmanager resta

[jira] [Commented] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856676#comment-16856676 ] wgcn commented on FLINK-12728: -- thanks ,Tao Yang .it does set  false.  We will try it. >

[jira] [Updated] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

[ https://issues.apache.org/jira/browse/FLINK-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-12728: - Description:     job can't restart when flink  job  has been running for a long time and then taskmanager resta

[jira] [Created] (FLINK-12728) taskmanager container can't launch on nodemanager machine because of kerberos

wgcn created FLINK-12728: Summary: taskmanager container can't launch on nodemanager machine because of kerberos Key: FLINK-12728 URL: https://issues.apache.org/jira/browse/FLINK-12728 Project: Flink

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701574#comment-16701574 ] wgcn commented on FLINK-10884: -- https://github.com/apache/flink/pull/7185 > Flink on yarn

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698537#comment-16698537 ] wgcn commented on FLINK-10884: -- thanks for your suggestion:D > Flink on yarn TM container

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698043#comment-16698043 ] wgcn commented on FLINK-10884: -- I think the  memory assigned to  jvm  not only contains  "

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693129#comment-16693129 ] wgcn commented on FLINK-10884: -- I found a unit test that per default the off heap memory is

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690502#comment-16690502 ] wgcn commented on FLINK-10884: -- Cool. it's my first experience in the community. I will fix

[jira] [Commented] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689067#comment-16689067 ] wgcn commented on FLINK-10884: -- Thanks for your watch. I found the configuration option, bu

[jira] [Updated] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wgcn updated FLINK-10884: - Labels: yarn (was: ) > Flink on yarn TM container will be killed by nodemanager because of the > exceeded p

[jira] [Created] (FLINK-10884) Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.

wgcn created FLINK-10884: Summary: Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory. Key: FLINK-10884 URL: https://issues.apache.org/jira/browse/FLINK-10884

[jira] [Commented] (FLINK-5770) Flink yarn session stop in non-detached model

[ https://issues.apache.org/jira/browse/FLINK-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668448#comment-16668448 ] wgcn commented on FLINK-5770: - your client maybe shutdown   you can use the arg -d  > Flink