-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] IndexingMasterFailoverIT.testMasterFailoverDuringIndexingWithMappingChanges fails #30844
Comments
Pinging @elastic/es-distributed |
@bleskes With acking being less lenient now, what happened is that one of the nodes did not ack the mapping update (but was disconnected instead), resulting in the failure of the index request. I suggest we stop checking for |
@ywelsch +1. My reasoning (I believe your reasoning is the same) is that an ack on putMapping means that the change was committed and it's OK for the primary to go into a waiting loop if the cluster state didn't arrive yet. Any failure to commit will result in a hard exception |
yes |
The failure was in an PR build https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request/10444/consoleText but after discussion with @ywelsch it doesn't seem to be related to the PR where it failed, but intstead might have been caused by #30672.
The failure doesn't reproduce:
The text was updated successfully, but these errors were encountered: