[HZ-1013 HZ-1059 HZ-1051] Fix hanging cluster safe query from common pool #21145
Conversation
This file contains 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
When all FJP#commonPool threads are busy querying isClusterSafe and partition assignments are not in sync (eg during initial partition arrangement), then there is no chance for an important callback to be executed after PartitionBackupReplicaAntiEntropyOperation is done, resulting in neither partition replica sync nor cluster-safe query being able to make any progress. The fix is to use the Hazelcast internal async executor (instead of the common pool) for the callback that processes replica antientropy operation result.
vbekiaris
added
Type: Defect
Team: Core
Source: Internal
vbekiaris
changed the title
ramizdundar
approved these changes
Apr 6, 2022
This was referenced Apr 12, 2022
|
The job Click to expand the log file-------------------------- ---------SUMMARY---------- -------------------------- [ERROR] COMPILATION ERROR : -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler_2/hazelcast-enterprise/hazelcast-enterprise/src/main/java/com/hazelcast/internal/nio/ssl/MemberTLSChannelInitializer.java:[32,37] error: incompatible types: InboundHandler[] cannot be converted to InboundHandler -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project hazelcast-enterprise: Compilation failure -------------------------- ---------ERRORS----------- -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler_2/hazelcast-enterprise/hazelcast-enterprise/src/main/java/com/hazelcast/internal/nio/ssl/MemberTLSChannelInitializer.java:[32,37] error: incompatible types: InboundHandler[] cannot be converted to InboundHandler -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler_2/hazelcast-enterprise/hazelcast-enterprise/src/main/java/com/hazelcast/internal/nio/ssl/MemberTLSChannelInitializer.java:[32,37] error: incompatible types: InboundHandler[] cannot be converted to InboundHandler -------------------------- |
AyberkSorgun
changed the title
AyberkSorgun
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When all
FJP#commonPoolthreads are busy queryingisClusterSafe(eg seems this can be the case when querying via PartitionService MBean)
and partition assignments are not in sync (eg during initial
partition arrangement), then there is no chance for an important
callback to be executed after
PartitionBackupReplicaAntiEntropyOperationis done, resulting in neither partition replica sync nor cluster-safe
query being able to make any progress.
The fix is to use the Hazelcast internal async executor (instead of
the common pool) for the callback that processes replica anti-entropy
operation result.
Fixes #19672
Fixes #18286
Fixes #19665
Checklist:
edit: see also #19672 (comment) on how this issue might occur