I’m working on a 2 node cluster with strong consistency enabled on both the nodes. When a node, which was down for some time is brought up, I can see that some migrations take place. I use the below mentioned command:
asadm -e "asinfo -v 'namespace/test_namespace' -l" | grep partition
Output(on my 2 node cluster)
dead_partitions=0 unavailable_partitions=0 migrate_tx_partitions_imbalance=0 migrate_tx_partitions_active=0 migrate_rx_partitions_active=0 migrate_tx_partitions_initial=4096 migrate_tx_partitions_remaining=4095 migrate_tx_partitions_lead_remaining=2012 migrate_rx_partitions_initial=4096 migrate_rx_partitions_remaining=4095 partition-tree-sprigs=256 sindex.num-partitions=32 dead_partitions=0 unavailable_partitions=0 migrate_tx_partitions_imbalance=0 migrate_tx_partitions_active=0 migrate_rx_partitions_active=0 migrate_tx_partitions_initial=4096 migrate_tx_partitions_remaining=4095 migrate_tx_partitions_lead_remaining=2082 migrate_rx_partitions_initial=4096 migrate_rx_partitions_remaining=4095 partition-tree-sprigs=256 sindex.num-partitions=32
Although the number of ‘
unavailable partitions’ becomes 0(once the 2nd node is brought up) but you’ll see that there are still some migrations remaining(both in tx and rx). Till the remaining migration count becomes 0, is this cluster-state stable(for read/write). If not, when should I worry about these counts(if at all) and which counts specifically?
I also couldn’t understand the count difference between
migrate_tx_partitions_lead_remaining. After reading the description, I had thought that there shouldn’t be any difference in both the counts since both the nodes are present in the roster. I’ll really appreciate if someone can clarify.