Skip to content

Conversation

@mdumandag
Copy link
Contributor

It might be the case that the replica node could not finish its
partition table initialization when it receives the backup operation
request from the primary node. That can cause the backup request to
be dropped which can result in test failure since there won't be any
backup acks from the replica node.

This won't be needed when the hazelcast/hazelcast#9398
is fixed. Until then, a call like map.get(1) should be enough as a
workaround.

See Also: hazelcast/hazelcast-nodejs-client#693

It might be the case that the replica node could not finish its
partition table initialization when it receives the backup operation
request from the primary node. That can cause the backup request to
be dropped which can result in test failure since there won't be any
backup acks from the replica node.

This won't be needed when the hazelcast/hazelcast#9398
is fixed. Until then, a call like `map.get(1)` should be enough as a
workaround.

See Also: hazelcast/hazelcast-nodejs-client#693
@mdumandag mdumandag merged commit 766c612 into hazelcast:master Nov 26, 2020
@mdumandag mdumandag deleted the possible-flaky-backup-acks-test branch November 26, 2020 14:49
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.

2 participants