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.

Sign up for GitHub

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

Jump to bottom

ClientTransactionalSetSplitBrainProtectionReadTest failed #18930

Closed
kwart opened this issue Jun 17, 2021 · 1 comment · Fixed by #19180
Closed

ClientTransactionalSetSplitBrainProtectionReadTest failed #18930

kwart opened this issue Jun 17, 2021 · 1 comment · Fixed by #19180
Assignees
@sancar
Labels
Module: ISet Source: Internal PR or issue was opened by an employee Team: Core Type: Test-Failure
Milestone
5.0

Comments

@kwart
Copy link
Member

kwart commented Jun 17, 2021

The com.hazelcast.client.splitbrainprotection.set.ClientTransactionalSetSplitBrainProtectionReadTest failed on master branch during PR builder run http://jenkins.hazelcast.com/job/Hazelcast-pr-builder/5637/

Build artifacts: https://console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-pr-builder/5637/

Stacktrace:

com.hazelcast.splitbrainprotection.SplitBrainProtectionException: Split brain protection exception: threeNodeSplitBrainProtectionRuleREAD has failed!
	at com.hazelcast.splitbrainprotection.impl.SplitBrainProtectionImpl.newSplitBrainProtectionException(SplitBrainProtectionImpl.java:279)
	at com.hazelcast.splitbrainprotection.impl.SplitBrainProtectionImpl.ensureNoSplitBrain(SplitBrainProtectionImpl.java:274)
	at com.hazelcast.splitbrainprotection.impl.SplitBrainProtectionImpl.ensureNoSplitBrain(SplitBrainProtectionImpl.java:269)
	at com.hazelcast.splitbrainprotection.impl.SplitBrainProtectionServiceImpl.ensureNoSplitBrain(SplitBrainProtectionServiceImpl.java:232)
	at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureNoSplitBrain(OperationRunnerImpl.java:338)
	at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:243)
	at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:469)
	at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:197)
	at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:137)
	at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.executeRun(OperationThread.java:123)
	at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
	at ------ submitted from ------.()
	at com.hazelcast.internal.util.ExceptionUtil.cloneExceptionWithFixedAsyncStackTrace(ExceptionUtil.java:279)
	at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.returnOrThrowWithGetConventions(InvocationFuture.java:112)
	at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveAndThrowIfException(InvocationFuture.java:100)
	at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:617)
	at com.hazelcast.collection.impl.queue.QueueProxySupport.invokeAndGet(QueueProxySupport.java:179)
	at com.hazelcast.collection.impl.queue.QueueProxySupport.invokeAndGet(QueueProxySupport.java:172)
	at com.hazelcast.collection.impl.queue.QueueProxySupport.size(QueueProxySupport.java:110)
	at com.hazelcast.collection.impl.queue.QueueProxyImpl.size(QueueProxyImpl.java:43)
	at com.hazelcast.splitbrainprotection.AbstractSplitBrainProtectionTest.initCluster(AbstractSplitBrainProtectionTest.java:247)
	at com.hazelcast.splitbrainprotection.AbstractSplitBrainProtectionTest.initTestEnvironment(AbstractSplitBrainProtectionTest.java:105)
	at com.hazelcast.client.splitbrainprotection.set.ClientTransactionalSetSplitBrainProtectionReadTest.setUp(ClientTransactionalSetSplitBrainProtectionReadTest.java:43)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeLazy(JUnitCoreWrapper.java:119)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:87)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
	at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
@kwart kwart added Team: Core Type: Test-Failure Source: Internal PR or issue was opened by an employee labels Jun 17, 2021
@kwart kwart added this to the 5.0 milestone Jun 17, 2021
This was referenced Jul 26, 2021
Closed
Closed
Closed
@mmedenjak
Copy link
Contributor

All of these seem related:
#18950
#18777
#18766
#18765
#18764

This was referenced Jul 26, 2021
Closed
Closed
sancar pushed a commit to sancar/hazelcast that referenced this issue Jul 26, 2021
Fixes SplitBrainTest start issues
a33a1a7 
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
@sancar sancar mentioned this issue Jul 26, 2021
Merged
mmedenjak pushed a commit that referenced this issue Jul 26, 2021
Fixes SplitBrainTest start issues (#19180)
8834585 
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
Fixes SplitBrainTest start issues
427f656 
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
Fixes SplitBrainTest start issues
d1ca409 
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
Fixes SplitBrainTest start issues
308aaa0 
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 sancar mentioned this issue Jul 27, 2021
Merged
sancar pushed a commit to sancar/hazelcast that referenced this issue Jul 27, 2021
Fixes SplitBrainTest start issues
3a70a65 
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 sancar mentioned this issue Jul 27, 2021
Merged
sancar pushed a commit to sancar/hazelcast that referenced this issue Jul 27, 2021
Fixes SplitBrainTest start issues
3f56245 
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 sancar mentioned this issue Jul 27, 2021
Merged
mmedenjak pushed a commit that referenced this issue Jul 28, 2021
Fixes SplitBrainTest start issues (#19189)
2d27fc3 
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
Fixes SplitBrainTest start issues (#19191)
bc678a5 
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
Fixes SplitBrainTest start issues (#19190)
05fad5d 
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
Assignees

@sancar sancar

Labels
Module: ISet Source: Internal PR or issue was opened by an employee Team: Core Type: Test-Failure
Projects
None yet
Milestone
5.0
Development

Successfully merging a pull request may close this issue.

Fixes SplitBrainTest start issues sancar/hazelcast
3 participants
@sancar @kwart @mmedenjak