These are chat archives for atomix/atomix
@aaudiber I think it’s probably a bug. I may recall something like that. Although, if commits are not managed correctly it can legitimately remove the session creation entry. In other words, if all the session’s commands were released and the session was expired/closed, Copycat will remove that open session entry.
I don’t really recall whether this was a bug in that implementation. We’ve been using the Atomix 2 Raft implementation for almost a year now and it’s much more stable. State machines are also much simpler and avoid this type of problem. It uses snapshots for log compaction and monitors throughput to avoid unnecessarily expensive operations while under load.
Atomix 2.1 documentation exists: http://atomix.io/docs/latest/user-manual/cluster-management/cluster-configuration/
It’s probably enough to get started. I’m just doing the most important documentation first. The release candidate will be this weekend or next week and the API will be stable after that.