Comment 1 for bug 2066585

The first instance of each database should indeed be running on the first node as per the bootstrap process. But once you add more machines and (only at the end) run a resize, it should spread the other ones on the extra nodes. Not sure if the process for that is already in place, but I understand that it is an intended feature.

There are many cases where it will be unbalanced (right after a bootstrap, or when you lose or reboot a node it will come back empty, etc.). This will need to be an active process that monitors and re-balance on demand.