You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by John Smith <ja...@gmail.com> on 2021/12/19 05:36:21 UTC
How to know if Job nodes are registered in cluster?
Hi running flink 1.10
I have 3 zookeeper nodes and 3 job nodes.
1 nodes has specifically indicated that it was granted leadership with
token.
The other 2 job nodes. Indicate: Starting ZooKeeperLeaderElectionService
ZooKeeperLeaderElectionService{leaderPath='/leader/resource_manager_lock'}.
So is that enough to know. Usually isn't there some message printed on each
node indicating to each other who is leader and who is "present"?
Re: How to know if Job nodes are registered in cluster?
Posted by John Smith <ja...@gmail.com>.
Ok so only the leader will indicate it's the leader. The other just say
they are waiting for a lock...
On Tue., Dec. 21, 2021, 9:42 a.m. David Morávek, <dm...@apache.org> wrote:
> Hi John,
>
> there is usually no need to run multiple JM, if you're able to start a new
> one quickly after failure (eg. when you're running on kubernetes). There is
> always only single active leader and other JMs effectively do nothing
> besides competing for the leadership. Zookeeper based HA uses the
> DefaultLeaderRetrievalService, which logs leadership information on DEBUG
> level.
>
> Best,
> D.
>
> On Sun, Dec 19, 2021 at 6:38 AM John Smith <ja...@gmail.com> wrote:
>
>> Hi running flink 1.10
>>
>> I have 3 zookeeper nodes and 3 job nodes.
>>
>> 1 nodes has specifically indicated that it was granted leadership with
>> token.
>> The other 2 job nodes. Indicate: Starting ZooKeeperLeaderElectionService
>> ZooKeeperLeaderElectionService{leaderPath='/leader/resource_manager_lock'}.
>> So is that enough to know. Usually isn't there some message printed on each
>> node indicating to each other who is leader and who is "present"?
>>
>
Re: How to know if Job nodes are registered in cluster?
Posted by David Morávek <dm...@apache.org>.
Hi John,
there is usually no need to run multiple JM, if you're able to start a new
one quickly after failure (eg. when you're running on kubernetes). There is
always only single active leader and other JMs effectively do nothing
besides competing for the leadership. Zookeeper based HA uses the
DefaultLeaderRetrievalService, which logs leadership information on DEBUG
level.
Best,
D.
On Sun, Dec 19, 2021 at 6:38 AM John Smith <ja...@gmail.com> wrote:
> Hi running flink 1.10
>
> I have 3 zookeeper nodes and 3 job nodes.
>
> 1 nodes has specifically indicated that it was granted leadership with
> token.
> The other 2 job nodes. Indicate: Starting ZooKeeperLeaderElectionService
> ZooKeeperLeaderElectionService{leaderPath='/leader/resource_manager_lock'}.
> So is that enough to know. Usually isn't there some message printed on each
> node indicating to each other who is leader and who is "present"?
>