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

[FORWARD PORT] Fail fast at startup for invalid WAN merge policy (#18875) #18928

Merged
merged 1 commit into from Jun 17, 2021

Conversation

ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Jun 17, 2021

forward port of #18875 (cherry-picked)

Modifications:
- Validate wan and split-brain merge policies at node-engine creation time to fail-fast at node start time.
- Print a warning log at execution phase of MergeOperation to catch unreasonable merge-policy 
configs that cannot be catch at start-up time. Example to this is, you have WAN replication between 
2 clusters, even though source cluster has per-entry-stats enabled, target cluster doesn't have it 
enabled. In this case, MergeOperation catches this anomaly and prints it as a warning.
@ahmetmircik ahmetmircik added this to the 5.0 milestone Jun 17, 2021
@hz-devops-test
Copy link

The job Hazelcast-pr-builder of your PR failed. (Hazelcast internal details: build log, artifacts).
Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log file
--------------------------
-------TEST FAILURE-------
--------------------------
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   IndexStatsChangingNumberOfMembersTest.testIndexStatsQueryingChangingNumberOfMembers:139->awaitStable:431->HazelcastTestSupport.assertTrueEventually:1362->HazelcastTestSupport.assertTrueEventually:1260->lambda$awaitStable$0:443 MemberPartitions={size=90, partitions=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 91]}, IndexImpl{partitionTracker=GlobalIndexPartitionTracker{partitionCount=271, state=State{stamp=516, indexedPartitions={size=84, partitions=[0, 1, 2, 6, 8, 9, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 91]}, pending=0}}} AbstractIndex{config=IndexConfig{name=this, type=HASH, attributes=[this]}}. Actual: -1
[ERROR] Errors: 
[ERROR]   TransactionalMultiMapSplitBrainProtectionWriteTest.setUp:78->AbstractSplitBrainProtectionTest.initTestEnvironment:105->AbstractSplitBrainProtectionTest.initCluster:247 ? SplitBrainProtection
[INFO] 
[ERROR] Tests run: 38545, Failures: 1, Errors: 1, Skipped: 1004
[INFO] 

[ERROR] There are test failures.

@hazelcast hazelcast deleted a comment from ahmetmircik Jun 17, 2021
@mmedenjak mmedenjak merged commit 86ee2a0 into hazelcast:master Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants