First of all, I want to thanks all LXD’s developpers for their very very great job. LXD is wonderfull !
I have some speed problem on my cluster, which can sometimes cause dramatical issues .
Nodes configuration :
- Debian 11
- LXD 4.24 rev 22710
- snapd 2.54.4
- 64 Gb of RAM
I run a LXD cluster with 3 nodes, geographically distant, managed by Pacemakerd. The storage is on a ceph cluster (SSD).
The 3 nodes dialog on public network (500mbps upload, 1gbps download for each one).
All 15 containers are running on same node. If this node has a problem, all containers move to another node.
The principal problem is that
lxc list is very slow.
lxc list --fast, is… fast, I played
lxc -c, and I can see that the retriving of IPv4 (I do not have IPv6) is particulary slow.
Here is some “time” test :
# time lxc ls -c nsL real 0m0.432s user 0m0.030s sys 0m0.065s
# time lxc ls -c nsL4 real 3m27.149s user 0m0.104s sys 0m0.088s
# time lxc ls real 3m25.567s user 0m0.070s sys 0m0.046s
The other speed problem that I can see, is that when I launch a new container, with the simple :
lxc launch images:debian/11 new_container it takes many minutes, and causes a timeout into the LXD API, that cause pacemaker to think the resources are down.
Thank you for your time.
I started a container which was stopped, and hasn’t IPv4 address, and now lxc list is mush faster :
# time lxc ls real 0m4.372s user 0m0.067s sys 0m0.068s
by the way, if I split the containers over 2 or 3 nodes,
lxc list will be very slow again.
I wonder if settings a virtual shared network over the nodes will tend to reduce this latence ?