I am talking about containers in ZFS. You lose them if the Cluster fails. Yes, they can be recovered if you can get that node running, but most of the time you cant reuse the container pool. It should not be data recovery export/import thing, it should just be re-add node to cluster.
The local/global database sync is a different thing. You require three to vote, and when there are two or one it freaks out. Read my comments on this here. How do you "upgrade" a cluster non-database member to database member?
Can you make LXD cluster work now, sure, but if you do an apt upgrade and reboot all your server, have to power down for some reason, you will go through hell. And you should not have to. LXD reminds me of my old boat, every time I go start it I have to through this whole procedure. I should not have to. It should go up and down 100% of the time. And if one node or all but one don’t work, then the working nodes should work. And if I bring back a node then it should work. It should not require black magic. I don’t mind if it is a manual thing to add, promote or demote a node. One should be able disable a cluster too, just like you enable one. And everything should always work locally. Solving this problem will help you guy save so much time on support, give system user friendliness and fault tolerance. There is also a problem on the booting process. My latest install require all kinds of poking every time I boot it. You can’t keep adding features and forget about this basic problem, think like a user not a programmer.
Believe me Stephane not trying to be a pain, I really like this product and I want to be the best.