What does it mean when several containers are NO in DATABASE, but otherwise seem to work ok

LXD
1

I have the following 5 containers, some of then are not “on database”, see below. What causes this and how who do I fix it. Thanks

±---------±-------------------------±---------±-------±------------------+
| NAME | URL | DATABASE | STATE | MESSAGE |
±---------±-------------------------±---------±-------±------------------+
| chemp | https://64.xxxx:8443 | NO | ONLINE | fully operational |
±---------±-------------------------±---------±-------±------------------+
| curlyjoe | https://64.xxxx:8443 | YES | ONLINE | fully operational |
±---------±-------------------------±---------±-------±------------------+
| joe | https://64.xxx:8443 | NO | ONLINE | fully operational |
±---------±-------------------------±---------±-------±------------------+
| larry | https://64.xxxx:8443 | YES | ONLINE | fully operational |
±---------±-------------------------±---------±-------±------------------+
| moe | https://64.xxx:8443 | YES | ONLINE | fully operational |
±---------±-------------------------±---------±-------±------------------+

2

YES means that the node has a copy of the distributed database. NO it means that it does not have a copy. Only 3 copies are necessary to keep cluster high availability, therefore once you reach 3 YES nodes all others that you add will be NO.

It’s all good, there’s nothing to fix.

3

I guess if I bring down one of the nodes that has a copy, one of the other will get a copy by itself?

4

If you remove a database node from the cluster, LXD will promote an existing node, yes.

It won’t do that if you just shut it down though, it only happens on removal.