Skip to content
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

More cleanup of TransportAddVotingConfigExclusionsActionTests #98356

Conversation

DaveCTurner
Copy link
Contributor

Rather than waiting for both cluster state updates, we should assert
that the second update has executed, performing the reconfiguration, by
the time the API returns.

Rather than waiting for both cluster state updates, we should assert
that the second update has executed, performing the reconfiguration, by
the time the API returns.
@DaveCTurner DaveCTurner added >test Issues or PRs that are addressing/adding tests :Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. v8.10.0 labels Aug 10, 2023
@DaveCTurner DaveCTurner requested a review from fcofdez August 10, 2023 13:47
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@elasticsearchmachine elasticsearchmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Aug 10, 2023
Copy link
Contributor

@fcofdez fcofdez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@DaveCTurner DaveCTurner merged commit 6417a4f into elastic:main Aug 11, 2023
@DaveCTurner DaveCTurner deleted the 2023/08/10/TransportAddVotingConfigExclusionsActionTests-more-cleanup branch August 11, 2023 09:16
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Aug 17, 2023
The docs for this API say the following:

> If the API fails, you can safely retry it. Only a successful response
> guarantees that the node has been removed from the voting
> configuration and will not be reinstated.

Unfortunately this isn't true today: if the request adds no exclusions
then we do not wait before responding. This commit makes the API wait
until all exclusions are really applied.

Backport of elastic#98386, plus the test changes from elastic#98146 and elastic#98356.
elasticsearchmachine pushed a commit that referenced this pull request Aug 17, 2023
The docs for this API say the following:

> If the API fails, you can safely retry it. Only a successful response
> guarantees that the node has been removed from the voting
> configuration and will not be reinstated.

Unfortunately this isn't true today: if the request adds no exclusions
then we do not wait before responding. This commit makes the API wait
until all exclusions are really applied.

Backport of #98386, plus the test changes from #98146 and #98356.
csoulios pushed a commit to csoulios/elasticsearch that referenced this pull request Aug 18, 2023
…c#98356)

Rather than waiting for both cluster state updates, we should assert
that the second update has executed, performing the reconfiguration, by
the time the API returns.
@DaveCTurner DaveCTurner restored the 2023/08/10/TransportAddVotingConfigExclusionsActionTests-more-cleanup branch June 17, 2024 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. >test Issues or PRs that are addressing/adding tests v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants