-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
DedicatedClusterSnapshotRestoreIT#testMasterShutdownDuringSnapshot fails in CI #24452
Labels
:Distributed Coordination/Network
Http and internode communication implementations
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
Comments
danielmitterdorfer
added
:Distributed Coordination/Network
Http and internode communication implementations
>test-failure
Triaged test failures from CI
>test
Issues or PRs that are addressing/adding tests
labels
May 3, 2017
abeyad
pushed a commit
to abeyad/elasticsearch
that referenced
this issue
May 11, 2017
Previously, if a master node updated the cluster state to reflect that a snapshot is completed, but subsequently failed before processing a cluster state to remove the snapshot from the cluster state, then the newly elected master would not know that it needed to clean up the leftover cluster state. This commit ensures that the newly elected master sees if there is a snapshot in the cluster state that is in the completed state but has not yet been removed from the cluster state. Closes elastic#24452
abeyad
pushed a commit
that referenced
this issue
May 11, 2017
Previously, if a master node updated the cluster state to reflect that a snapshot is completed, but subsequently failed before processing a cluster state to remove the snapshot from the cluster state, then the newly elected master would not know that it needed to clean up the leftover cluster state. This commit ensures that the newly elected master sees if there is a snapshot in the cluster state that is in the completed state but has not yet been removed from the cluster state. Closes #24452
abeyad
pushed a commit
that referenced
this issue
May 11, 2017
Previously, if a master node updated the cluster state to reflect that a snapshot is completed, but subsequently failed before processing a cluster state to remove the snapshot from the cluster state, then the newly elected master would not know that it needed to clean up the leftover cluster state. This commit ensures that the newly elected master sees if there is a snapshot in the cluster state that is in the completed state but has not yet been removed from the cluster state. Closes #24452
abeyad
pushed a commit
that referenced
this issue
May 11, 2017
Previously, if a master node updated the cluster state to reflect that a snapshot is completed, but subsequently failed before processing a cluster state to remove the snapshot from the cluster state, then the newly elected master would not know that it needed to clean up the leftover cluster state. This commit ensures that the newly elected master sees if there is a snapshot in the cluster state that is in the completed state but has not yet been removed from the cluster state. Closes #24452
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Network
Http and internode communication implementations
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
gradle :core:integTest -Dtests.seed=E02060E9AA99A891 -Dtests.class=org.elasticsearch.snapshots.DedicatedClusterSnapshotRestoreIT -Dtests.method="testMasterShutdownDuringSnapshot" -Dtests.security.manager=true -Dtests.locale=es-BO -Dtests.timezone=Africa/Cairo
build output for the failing test
The text was updated successfully, but these errors were encountered: