Ali Beyad 3da04293f3 Cannot force allocate primary to a node where the shard already exists (#22031) ...

Before, it was possible that the SameShardAllocationDecider would allow
force allocation of an unassigned primary to the same node on which an
active replica is assigned.  This could only happen with shadow replica
indices, because when a shadow replica primary fails, the replica gets
promoted to primary but in the INITIALIZED state, not in the STARTED
state (because the engine has specific reinitialization that must take
place in the case of shadow replicas).  Therefore, if the now promoted
primary that is initializing fails also, the primary will be in the
unassigned state, because replica to primary promotion only happens when
the failed shard was in the started state.  The now unassigned primary
shard will go through the allocation deciders, where the
SameShardsAllocationDecider would return a NO decision, but would still
permit force allocation on the primary if all deciders returned NO.

This commit implements canForceAllocatePrimary on the
SameShardAllocationDecider, which ensures that a primary cannot be
force allocated to the same node on which an active replica already
exists.

2016-12-08 12:21:19 -05:00

..

licenses

Add version 5.0.3

2016-11-29 18:34:55 -05:00

src

Cannot force allocate primary to a node where the shard already exists (#22031)

2016-12-08 12:21:19 -05:00

build.gradle

Update Joda Time to version 2.9.5 (#21468)

2016-11-10 17:32:46 +01:00