These are chat archives for atomix/atomix
@hntd187 Sorry I've been busy...
If you want to replace the cluster, you might be able to trick the client by implementing a
ServerSelectionStrategy and returning a different set of addresses. That's obviously a hack. It would be better to just close/reconnect (not so sure that works) or create a new client.
MEMORYfor testing state machines and what not right now. Losing the term is very problematic for more reasons than just the one you mentioned. But concerns about the leader election process are the least of your worries if you're using an in-memory log. The real problem is, if a majority of servers go down then basically any server can win an election when a quorum is restored, meaning the cluster may just delete all your state.
Yes. Heap memory is just used right now for stability. I haven't really tested off heap memory since it's just used for testing.
That's correct. The client could expire its own session, but there's not really a good reason to do that. Even if the entire cluster goes down, once the client's able to start communicating with it again, its session may still be active. The cluster can't expire a session if a majority is down. There's no reason to lose consistency guarantees proactively if it may not be necessary.