[SOLR-8554] RebalanceLeader and ForceLeader APIs should be part of OverseerCollectionMessageHandler

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Varun Thacker
• Created: 15/Jan/16 11:03
• Updated: 20/Jun/16 12:13

Description

I think RebalanceLeader and ForceLeader API calls should be part of the OverseerCollectionMessageHandler.

There are two reasons for this -
1. If the API is implemented within the OverseerCollectionMessageHandler the Overseer provides us with concurrency guarantees i.e two calls against a collection can't be executed simultaneously .
An example, a delete shard was fired and simultaneously a force leader was fired. Now say the replica which was meant to be deleted became the new leader.
2. Less important that 1 , but if the API is implemented within the OverseerCollectionMessageHandler , we can provide an async option in these APIs

Issue Links

• is depended upon by: SOLR-9226 Automatically fire FORCELEADER if shard leader is missing