These are chat archives for atomix/atomix
We are no longer monitoring this channel, please join Slack! https://join.slack.com/t/atomixio/shared_invite/enQtNDgzNjA5MjMyMDUxLTVmMThjZDcxZDE3ZmU4ZGYwZTc2MGJiYjVjMjFkOWMyNmVjYTc5YjExYTZiOWFjODlkYmE2MjNjYzZhNjU2MjY
PERSISTENTnodes being explicitly listed anyways
PERSISTENTnodes after startup as long as they’re not participating in consensus.
CLIENTnodes and have just two node types
AtomixClusterclass that’s independently runnable without
atomix-core. This would provide a class that makes it possible to do cluster management and communication independent of the primitives, and allow us to make assumptions that using the
Atomixclass indicates intent to use primitives.
EPHEMERALnodes participating in consensus, and that makes it feasible to learn about node types assuming at least the
Addressfor those nodes is provided at startup. But we’d still need to have some way to indicate which nodes are participating in consensus at startup, and no consensus node can be missing. But the semantics of
PERSISTENTnodes make sense for consensus anyways. That is, even though a node is not alive it’s still part of the cluster and is counted towards votes.
PERSISTENT) nodes must be explicitly listed at startup. Non-consensus (
EPHEMERAL) nodes don’t have to be listed at all and can be discovered via the consensus nodes.