IGNITE-28123 ClientPrimaryReplicaTracker: avoid null-partitions failure when primary-replica lookup completes exceptionally#7741
Open
Lalant wants to merge 2 commits intoapache:mainfrom
Conversation
…plete exceptionally while resolving primary replicas. In ClientPrimaryReplicaTracker.primaryReplicasAsyncInternal, the exceptional path was not terminated for non-TableNotFound errors, and execution could continue into result construction with partitions == null, causing a secondary failure (NullPointerException from unboxing).
Lalant
force-pushed
the
ignite-28123-ClientPrimaryReplicaTracker-avoid-null-partitions-failure
branch
from
ebe0c81 to
a7e4de0
Compare
ptupitsyn
approved these changes
Mar 10, 2026
...ient-handler/src/main/java/org/apache/ignite/client/handler/ClientPrimaryReplicaTracker.java
Outdated
Show resolved
Hide resolved
Lalant
force-pushed
the
ignite-28123-ClientPrimaryReplicaTracker-avoid-null-partitions-failure
branch
2 times, most recently
from
3803392 to
e408967
Compare
Lalant
force-pushed
the
ignite-28123-ClientPrimaryReplicaTracker-avoid-null-partitions-failure
branch
from
e408967 to
4542f1d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Under node restarts, partition assignment lookup may complete exceptionally while resolving primary replicas.
In ClientPrimaryReplicaTracker.primaryReplicasAsyncInternal, the exceptional path was not terminated for non-TableNotFound errors, and execution could continue into result construction with partitions == null, causing a secondary failure (NullPointerException from unboxing).
https://issues.apache.org/jira/browse/IGNITE-28123