Put a fake allocation id on allocate stale primary command#34140

Merged

vladimirdolzhenko merged 31 commits intoelastic:masterfrom vladimirdolzhenko:forced_allocation_allocation_id

Nov 7, 2018

+352-40

Commits on Sep 28, 2018

Put a fake allocation id on allocate stale primary command; remove it after recovery is done
Vladimir Dolzhenko
committed

Commits on Sep 29, 2018

added a test case to spot the problem if allocation id is adjusted before recovery is done (historyUUID is adjusted):
Vladimir Dolzhenko
committed

Commits on Sep 30, 2018

Merge remote-tracking branch 'remotes/origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed

Commits on Oct 1, 2018

simplify test case to spot the problem if allocation id is adjusted before recovery is done (historyUUID is adjusted)
Vladimir Dolzhenko
committed

Commits on Oct 2, 2018

extended testAllocateCommand: added AllocateStalePrimaryAllocationCommand
Vladimir Dolzhenko
committed
enforced check that there is only one allocation id on adding/removing fake allocation id
Vladimir Dolzhenko
committed

Commits on Oct 3, 2018

fix BalanceConfigurationTests: using TestGatewayAllocator instead of NoopGatewayAllocator that generated inconsistent cluster state
Vladimir Dolzhenko
committed
enforce check for fake_allocation: for existing store it could be only FORCE_STALE_PRIMARY_INSTANCE
Vladimir Dolzhenko
committed
Merge remote-tracking branch 'remotes/origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed

Commits on Oct 5, 2018

Merge remote-tracking branch 'remotes/origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed

Commits on Oct 25, 2018

inline addAllocationId; add assert on initializingShard.allocationId() equal to startedShard.allocationId()
Vladimir Dolzhenko
committed
java doc for FORCED_ALLOCATION_ID; use front and back underscore for the fake allocation id
Vladimir Dolzhenko
committed

Commits on Oct 26, 2018

S/R deserves its own allocation id
Vladimir Dolzhenko
committed

Commits on Oct 29, 2018

fix assert on initializingShard.allocationId() equal to startedShard.allocationId()
Vladimir Dolzhenko
committed
fixed index routing table validation message for fake allocation id case
Vladimir Dolzhenko
committed
extract AllocateStalePrimaryCommand to its own test method
Vladimir Dolzhenko
committed
simplify AllocationIdIT
Vladimir Dolzhenko
committed

Commits on Oct 30, 2018

simplify AllocationIdIT; don't restart master
Vladimir Dolzhenko
committed
Merge remote-tracking branch 'remotes/origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed
after merge compilation fix
Vladimir Dolzhenko
committed

Commits on Nov 5, 2018

Merge branch 'origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed
move updates earlier and reuse it
Vladimir Dolzhenko
committed
drop getNodeIdByName as AllocateStalePrimaryAllocationCommand can use node name instead of node id
Vladimir Dolzhenko
committed
dropped unnecessary settings
Vladimir Dolzhenko
committed
handle single historyUUID
Vladimir Dolzhenko
committed
reuse ESIntegTestCase.createIndex
Vladimir Dolzhenko
committed
drop redundant assertBusy
Vladimir Dolzhenko
committed
comment on the reason behind the test
Vladimir Dolzhenko
committed
S&R leftover
Vladimir Dolzhenko
committed
drop useless open index (index is still opened)
Vladimir Dolzhenko
committed
Merge remote-tracking branch 'remotes/origin/master' into forced_allocation_allocation_id
Vladimir Dolzhenko
committed