GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/3578
[FLINK-6134] Set UUID(0L, 0L) as default leader session id
Before the default leader session id was null in the standalone case.
However, in the ZooKeeper
case null indicated that there was no active leader available. With this
commit, the default
leader id will be set to UUID(0L, 0L). This allows the uniform treatment of
null denoting that
there is no active leader across the standalone and the ZooKeeper case.
With this change, the FlinkActors will now ignore all LeaderSessionMessages
if the actor's
leader id field is null. This indicates that the FlinkActor does not know
the current leader.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink introduceDefaultLeaderId
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3578.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3578
----
commit 0fb0fe0a99de80379da2b758b06d333a7646c478
Author: Till Rohrmann <[email protected]>
Date: 2017-03-20T17:15:57Z
[FLINK-6134] Set UUID(0L, 0L) as default leader session id
Before the default leader session id was null in the standalone case.
However, in the ZooKeeper
case null indicated that there was no active leader available. With this
commit, the default
leader id will be set to UUID(0L, 0L). This allows the uniform treatment of
null denoting that
there is no active leader across the standalone and the ZooKeeper case.
With this change, the FlinkActors will now ignore all LeaderSessionMessages
if the actors's
leader id field is null. This indicates that the FlinkActor does not know
the current leader.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
