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

Avoid NPE when disassociateDeadNodes is executed for a node present in the desired balance #91659

Merged
merged 9 commits into from Nov 18, 2022

Conversation

idegtiarenko
Copy link
Contributor

An NPE is thrown when executing disassociateDeadNodes for a node that is
present in a desired balance failing corresponding master state update task.
As a result this node can no longer join cluster after restarting as it
remains in a cluster state.

Closes: #91517

@idegtiarenko idegtiarenko added >bug :Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) Team:Distributed Meta label for distributed team auto-backport-and-merge Automatically create backport pull requests and merge when ready v8.6.0 v8.7.0 labels Nov 17, 2022
@elasticsearchmachine
Copy link
Collaborator

Hi @idegtiarenko, I've created a changelog YAML for you.

@idegtiarenko idegtiarenko changed the title Avoid NPE when disassociateDeadNodes Avoid NPE when disassociateDeadNodes is executed for a node present in the desired balance Nov 17, 2022
@idegtiarenko idegtiarenko marked this pull request as ready for review November 18, 2022 08:16
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine
Copy link
Collaborator

Hi @idegtiarenko, I've updated the changelog YAML for you.

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

Could we assert the node is not-null in the place where the NPE was happening? Would have been good to see it as an immediate failure at that point, let's avoid any recurrence and document the assumption here.

Otherwise LGTM (one typo nit) no need for another review.

@idegtiarenko idegtiarenko merged commit 4a392e2 into elastic:main Nov 18, 2022
idegtiarenko added a commit to idegtiarenko/elasticsearch that referenced this pull request Nov 18, 2022
@idegtiarenko idegtiarenko deleted the fix_reconciliation branch November 18, 2022 10:42
elasticsearchmachine pushed a commit that referenced this pull request Nov 18, 2022
craigtaverner added a commit to craigtaverner/elasticsearch that referenced this pull request Nov 21, 2022
craigtaverner added a commit that referenced this pull request Nov 21, 2022
* Regenerated release notes for three bug fixes

* #91659
* #91710
* #91622

* Added highlight notes for cartesian centroid and bounds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport-and-merge Automatically create backport pull requests and merge when ready >bug :Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) Team:Distributed Meta label for distributed team v8.6.0 v8.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] rolling-upgrade-multi-cluster tests failing to start node
3 participants