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

Fix NPE in toString of FailedShard #64770

Conversation

original-brownbear
Copy link
Member

The concatenation took precedence over the null check, leading to an NPE
because null was passed to ExceptionsHelper.stackTrace(failure)).

Just saw this in a test failure and it might be the cause because this kills the execution of AllocationService#applyFailedShards

The concatenation took precendence over the null check, leading to an NPE
because `null` was passed to `ExceptionsHelper.stackTrace(failure))`.
@original-brownbear original-brownbear added >non-issue :Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v8.0.0 v7.11.0 labels Nov 9, 2020
@elasticmachine
Copy link
Collaborator

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

Copy link
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

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

LGTM.

@original-brownbear
Copy link
Member Author

Thanks Tanguy & Henning!

@original-brownbear original-brownbear merged commit c53b0ea into elastic:master Nov 9, 2020
@original-brownbear original-brownbear deleted the fix-npe-in-failed-shard branch November 9, 2020 13:31
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Nov 9, 2020
The concatenation took precedence over the null check, leading to an NPE
because `null` was passed to `ExceptionsHelper.stackTrace(failure))`.
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Nov 9, 2020
The concatenation took precedence over the null check, leading to an NPE
because `null` was passed to `ExceptionsHelper.stackTrace(failure))`.
original-brownbear added a commit that referenced this pull request Nov 9, 2020
The concatenation took precedence over the null check, leading to an NPE
because `null` was passed to `ExceptionsHelper.stackTrace(failure))`.
original-brownbear added a commit that referenced this pull request Nov 9, 2020
The concatenation took precedence over the null check, leading to an NPE
because `null` was passed to `ExceptionsHelper.stackTrace(failure))`.
@original-brownbear original-brownbear restored the fix-npe-in-failed-shard branch December 6, 2020 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>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 v7.10.1 v7.11.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants