These are chat archives for atomix/atomix
NettyTransportbefore the release, and that effectively means running a cluster in a single process which should work fine
expire(ServerSession)method and will release the lock and grant it to another session if there's one waiting for it.
CopycatServer.Builder. When a client/replica registers a session, the leader through which the session is registered assigns a timeout to the client/replica's session. The client/replica (or the underlying
CopycatClientsends keep-alives at 1/2 the session timeout. If a leader doesn't here from the client for a session timeout, it expires the session and all state machines can react to the expired session.
LockContexton which you can register a listener to detect when the lock is lost due to connection issues.
MEMORYstorage, there was no real way to stop those collisions from happening? Could that have been my problem?