You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-zh@flink.apache.org by Lijie Wang <wa...@126.com> on 2020/05/27 05:52:13 UTC
回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
这是因为你的 cluster 已经在运行了,你重复执行了 start-cluster.sh。如果想要重启cluster,可以先 stop-cluster.sh, 然后再 start-cluster.sh
在2020年05月27日 13:39,smq<37...@qq.com> 写道:
hi
哪位大神知道这个问题怎么解决吗.谢谢了
[root@node01 bin]# start-cluster.sh
Starting HA cluster with 2 masters.
[INFO] 5 instance(s) of standalonesession are already running on node01.
Starting standalonesession daemon on host node01.
[INFO] 1 instance(s) of standalonesession are already running on node02.
Starting standalonesession daemon on host node02.
[INFO] 1 instance(s) of taskexecutor are already running on node01.
Starting taskexecutor daemon on host node01.
[INFO] 3 instance(s) of taskexecutor are already running on node02.
Starting taskexecutor daemon on host node02.
[INFO] 6 instance(s) of taskexecutor are already running on node03.
Starting taskexecutor daemon on host node03.
回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
Posted by smq <37...@qq.com>.
还是不行,可能是别的原因,昨天还好好的,今天不知道搞了什么就这样了。看了日志说resourcemanager拒绝连接。
---原始邮件---
发件人: "Lijie Wang"<wanglijie95@126.com>
发送时间: 2020年5月27日(周三) 中午1:59
收件人: "user-zh@flink.apache.org"<user-zh@flink.apache.org>;
主题: 回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
jps 看一下进程号,直接 kill 掉也可以吧。
在2020年05月27日 13:55,smq<374060171@qq.com> 写道:
执行start-cluster.sh之后是这样
[root@node01 bin]# stop-cluster.sh
No taskexecutor daemon (pid: 11978) is running anymore on node01.
No taskexecutor daemon (pid: 5885) is running anymore on node02.
No taskexecutor daemon (pid: 4529) is running anymore on node03.
No standalonesession daemon (pid: 11633) is running anymore on node01.
No standalonesession daemon (pid: 5554) is running anymore on node02.
再次start之后还是跟刚开始一样,不知道有么有别的方法stop掉
------------------&nbsp;原始邮件&nbsp;------------------
发件人:&nbsp;"Lijie Wang"<wanglijie95@126.com&gt;;
发送时间:&nbsp;2020年5月27日(星期三) 中午1:52
收件人:&nbsp;"user-zh@flink.apache.org"<user-zh@flink.apache.org&gt;;
主题:&nbsp;回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
这是因为你的 cluster 已经在运行了,你重复执行了 start-cluster.sh。如果想要重启cluster,可以先 stop-cluster.sh, 然后再 start-cluster.sh
在2020年05月27日 13:39,smq<374060171@qq.com&gt; 写道:
hi
哪位大神知道这个问题怎么解决吗.谢谢了
[root@node01 bin]# start-cluster.sh
Starting HA cluster with 2 masters.
[INFO] 5 instance(s) of standalonesession are already running on node01.
Starting standalonesession daemon on host node01.
[INFO] 1 instance(s) of standalonesession are already running on node02.
Starting standalonesession daemon on host node02.
[INFO] 1 instance(s) of taskexecutor are already running on node01.
Starting taskexecutor daemon on host node01.
[INFO] 3 instance(s) of taskexecutor are already running on node02.
Starting taskexecutor daemon on host node02.
[INFO] 6 instance(s) of taskexecutor are already running on node03.
Starting taskexecutor daemon on host node03.
回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
Posted by Lijie Wang <wa...@126.com>.
jps 看一下进程号,直接 kill 掉也可以吧。
在2020年05月27日 13:55,smq<37...@qq.com> 写道:
执行start-cluster.sh之后是这样
[root@node01 bin]# stop-cluster.sh
No taskexecutor daemon (pid: 11978) is running anymore on node01.
No taskexecutor daemon (pid: 5885) is running anymore on node02.
No taskexecutor daemon (pid: 4529) is running anymore on node03.
No standalonesession daemon (pid: 11633) is running anymore on node01.
No standalonesession daemon (pid: 5554) is running anymore on node02.
再次start之后还是跟刚开始一样,不知道有么有别的方法stop掉
------------------ 原始邮件 ------------------
发件人: "Lijie Wang"<wanglijie95@126.com>;
发送时间: 2020年5月27日(星期三) 中午1:52
收件人: "user-zh@flink.apache.org"<user-zh@flink.apache.org>;
主题: 回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
这是因为你的 cluster 已经在运行了,你重复执行了 start-cluster.sh。如果想要重启cluster,可以先 stop-cluster.sh, 然后再 start-cluster.sh
在2020年05月27日 13:39,smq<374060171@qq.com> 写道:
hi
哪位大神知道这个问题怎么解决吗.谢谢了
[root@node01 bin]# start-cluster.sh
Starting HA cluster with 2 masters.
[INFO] 5 instance(s) of standalonesession are already running on node01.
Starting standalonesession daemon on host node01.
[INFO] 1 instance(s) of standalonesession are already running on node02.
Starting standalonesession daemon on host node02.
[INFO] 1 instance(s) of taskexecutor are already running on node01.
Starting taskexecutor daemon on host node01.
[INFO] 3 instance(s) of taskexecutor are already running on node02.
Starting taskexecutor daemon on host node02.
[INFO] 6 instance(s) of taskexecutor are already running on node03.
Starting taskexecutor daemon on host node03.
回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
Posted by smq <37...@qq.com>.
执行start-cluster.sh之后是这样
[root@node01 bin]# stop-cluster.sh
No taskexecutor daemon (pid: 11978) is running anymore on node01.
No taskexecutor daemon (pid: 5885) is running anymore on node02.
No taskexecutor daemon (pid: 4529) is running anymore on node03.
No standalonesession daemon (pid: 11633) is running anymore on node01.
No standalonesession daemon (pid: 5554) is running anymore on node02.
再次start之后还是跟刚开始一样,不知道有么有别的方法stop掉
------------------ 原始邮件 ------------------
发件人: "Lijie Wang"<wanglijie95@126.com>;
发送时间: 2020年5月27日(星期三) 中午1:52
收件人: "user-zh@flink.apache.org"<user-zh@flink.apache.org>;
主题: 回复:flink集群启动显示正在运行instance多,StandaloneSessionClusterEntrypoint启动后被kill
这是因为你的 cluster 已经在运行了,你重复执行了 start-cluster.sh。如果想要重启cluster,可以先 stop-cluster.sh, 然后再 start-cluster.sh
在2020年05月27日 13:39,smq<374060171@qq.com> 写道:
hi
哪位大神知道这个问题怎么解决吗.谢谢了
[root@node01 bin]# start-cluster.sh
Starting HA cluster with 2 masters.
[INFO] 5 instance(s) of standalonesession are already running on node01.
Starting standalonesession daemon on host node01.
[INFO] 1 instance(s) of standalonesession are already running on node02.
Starting standalonesession daemon on host node02.
[INFO] 1 instance(s) of taskexecutor are already running on node01.
Starting taskexecutor daemon on host node01.
[INFO] 3 instance(s) of taskexecutor are already running on node02.
Starting taskexecutor daemon on host node02.
[INFO] 6 instance(s) of taskexecutor are already running on node03.
Starting taskexecutor daemon on host node03.