Lenny Primak

In general, the way I am testing this by running https://github.com/flowlogix/hazelcast-issues/ CacheTester, which is an interactive tool that exercises locking and maps (Hazelcast in general). You can Ctrl-Z it and...

Apparently, I am not the only one who is having this issue. Hopefully the test reproducers can shed some more light on this.

Thanks for your feedback @arodionov > This behaviour is by design. We shouldn’t allow the restarted member to join back the cluster automatically My current CP use case is only...

> This is also by design - if a cluster lost the majority of its members it will be blocked and should be recovered manually Just tested this scenario, and...

Another issue... I have tried to auto-reset the subsystem via code when CP goes down to one member, but I get the below exception... Currently, there is no way to...

Another one: shutdown is not possible in the "unusable" state. What that means in practice is that a CP cluster can't be cleanly and quickly shut down. It gets into...

Thank you for listening @arodionov I understand that this is a difficult problem, but I am trying to make already fantastic product better.

@arodionov I have added a new test, `whenMemberExitsNormally_thenReceiveEvents` to hazelcast/src/test/java/com/hazelcast/cp/CPGroupAvailabilityListenerTest.java in https://github.com/hazelcast/hazelcast/pull/24903 This test is failing and clearly demonstrates incorrect behavior described here: https://github.com/hazelcast/hazelcast/issues/24897#issuecomment-1610009241

@arodionov Thanks! Looks great!

After some back-and-fourth, it's become clear that whenMemberExitsNormally_thenReceiveEvents is no longer necessary after the PR and is working correctly.