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
ClusterMetadataServicelevel. Working mostly on testing and documentation for the next few weeks. I’ll hack out some tests to reproduce it right now and figure out what’s going on.
I realized something while playing with those reconfiguration tests... there’s a problem with the fact partitions are still based on the number of nodes in the cluster. When I start a single node cluster and then add a second node to it, if the number of “coordination” (Raft) partitions is not configured, the first node is started with one partition and the second with two partitions. The second node fails startup because the second partition can’t join a non-existent second Raft partition. This is far too difficult to understand IMO.
There are a few options here: either the number of partitions needs to be replicated in the cluster metadata, or the number of partitions maybe needs to be a required configuration, or the default number of partitions needs to be static, or the Raft primitives need to support repartitioning. The last option is a long-term feature that should probably be left for Atomix 2.2