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
com.hazelcast.client.splitbrainprotection.queue.ClientQueueSplitBrainProtectionWriteTest.remove_splitBrainProtection #18950
Labels
Module: IQueue
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
Type: Test-Failure
Milestone
Comments
mmedenjak
added
Source: Internal
PR or issue was opened by an employee
Module: IQueue
labels
Jun 28, 2021
Moving to 5.0 to check in stabilization period. |
This was referenced Jul 26, 2021
Also this - #18930 |
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 26, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930
mmedenjak
pushed a commit
that referenced
this issue
Jul 26, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes #18950 fixes #18777 fixes #18766 fixes #18765 fixes #18764 fixes #18930
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 27, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930 (cherry picked from commit a33a1a7)
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 27, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930 (cherry picked from commit a33a1a7)
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 27, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930 (cherry picked from commit a33a1a7)
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 27, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930 (cherry picked from commit a33a1a7)
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Jul 27, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes hazelcast#18950 fixes hazelcast#18777 fixes hazelcast#18766 fixes hazelcast#18765 fixes hazelcast#18764 fixes hazelcast#18930 (cherry picked from commit a33a1a7)
mmedenjak
pushed a commit
that referenced
this issue
Jul 28, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes #18950 fixes #18777 fixes #18766 fixes #18765 fixes #18764 fixes #18930 (cherry picked from commit a33a1a7)
mmedenjak
pushed a commit
that referenced
this issue
Jul 28, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes #18950 fixes #18777 fixes #18766 fixes #18765 fixes #18764 fixes #18930 (cherry picked from commit a33a1a7)
mmedenjak
pushed a commit
that referenced
this issue
Jul 28, 2021
SplitBrainStatus is set by a single thread at the hazelcast instance start in an async manner. Therefore, we are not sure that a the status is set when the test starts. Adding an eventually check at the start so that we make sure we have the min-size cluster for all split brain protections before we actually split the cluster fixes #18950 fixes #18777 fixes #18766 fixes #18765 fixes #18764 fixes #18930 (cherry picked from commit a33a1a7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Module: IQueue
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
Type: Test-Failure
4.2.z (commit b80b074)
Failed on Zulu JDK 11: http://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-4.maintenance-ZuluJDK11/5/testReport/com.hazelcast.client.splitbrainprotection.queue/ClientQueueSplitBrainProtectionWriteTest/remove_splitBrainProtection_splitBrainProtectionType_READ_WRITE_/
It failed with option
[splitBrainProtectionType:READ_WRITE]
.Stacktrace:
Standard output:
The text was updated successfully, but these errors were encountered: