-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cancel replica recovery on another sync option copy found #12421
Cancel replica recovery on another sync option copy found #12421
Conversation
/** | ||
* A better replica location is identified and causes the existing replica allocation to be cancelled. | ||
*/ | ||
REALOCATED_REPLICA; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we miss an L here REAL_L_OCATED
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:)
This is awesome. LGTM. Left some small suggestions... |
OH. We probably need to document this. I'm also wondering if a release highlight is in order... |
@bleskes pushed changes, @clintongormley I am not sure where to document this? |
still awesome |
This is awesome and it's definitely a worthwhile release highlight! |
@kimchy should be documented here i think: https://www.elastic.co/guide/en/elasticsearch/reference/master/delayed-allocation.html I can add a note if you like. What do you mean by (eventually) in your PR description? |
When a replica is initializing from the primary, and we find a better node that has full sync id match, it is better to cancel the existing replica allocation and allocate it to the new node with sync id match (eventually)
2bfe004
to
fc90c2a
Compare
thanks @clintongormley!, I just pushed it. What I meant by eventually is that we cancel the replica allocation to the node, and then we will try and allocate it to the node with the sync id match, but on that node, we might be throttling allocation, so it will end up getting assigned to it, but not right away, in order to respect the allocation deciders. |
Docs added in c22e179 |
When a replica is initializing from the primary, and we find a better node that has full sync id match, it is better to cancel the existing replica allocation and allocate it to the new node with sync id match (eventually)