[CONTROLLER-1504] Entity Ownership Service: on restart of majority of nodes listeners receive isOwner=True before registering candidate Created: 29/Mar/16  Updated: 04/Apr/16  Resolved: 04/Apr/16

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: Beryllium
Fix Version/s: None

Type: Bug
Reporter: Amit Mandke Assignee: Amit Mandke
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 5613

 Description   

In a case when majority of node in cluster are restarted, Entity ownership service sends isOwner=True to Listener on a node that is not registered as candidate yet after a restart of a node.

Ex:
There is 3 node cluster with, member-1, member-2, member-3 as its cluster members.

Lets say member-1 is EntityOwnershipShard Leader.

Then all three members register as candidate for "Entity1", and member-1 becomes owner of "Entity1".

After this if member-1 and member-2 both restart. Now if the application code to register is written in such a way that it adds listener first and then register itself as candidate when "ready" to become candidate of "Entity1". However, one of those started nodes receive "isOwner" way ahead and then the register candidate code goes through.

Here the consumer of the service is expecting that the the member should not be a candidate unless registered for. However during restarts the candidates get added automatically even before registration.

So there is need to separate the case of nodes going in partition and restart of nodes.


Generated at Wed Feb 07 19:55:43 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.