These are chat archives for atomix/atomix
INFO [copycat-client-io-1] default io.atomix.catalyst.transport.NettyClient || Connecting to mobile/127.0.0.1:4444
shutdownon a server it just shuts the server down without removing the server from the cluster. So, if you have a three node cluster and you shut down two nodes, you’re losing a majority of the cluster. Alternatively, if you were to
leavethe cluster then the cluster would shrink to one node. The problem with
shutdownwhen you lose a majority is the client can’t connect to unregister its session. So, this could be fixed by just stopping the client if it can’t connect to unregister its session and just let its session expire. Maybe the client should still just shut down and return an exception to indicate that it couldn’t explicitly unregister its session so we can still imply that its session will have to expire in the cluster.
closed its session is no longer present. For example, one could
closea client that holds a lock and expect that the lock is released when the client is shut down, but that may not be the case if we allow the session to expire instead. So, the client should probably attempt once to unregister its session and shutdown gracefully and then shutdown and fail the
CompletableFuturewith some exception if it was unable to unregister its session.
AtomixReplica#shutdownmethod to progress when a majority of the cluster is down
leaveon all nodes… that will first remove the node from the cluster and then shut it down
shutdown… in that case at least your data stays on disk