Slow response between XCP-NG and cloud stack syncing
-
We have created two clusters in XCP-ng:
A Management Cluster consisting of 2 physical hosts.
A Compute Cluster consisting of 5 physical hosts.We deployed the CloudStack management components on VMs running in the Management Cluster.
During HA testing, we observed that when a VM is shut down from the XCP-ng side, CloudStack continues to display the VM as running for approximately 10 minutes before the status is updated.
We have performed extensive validation on the CloudStack side and have not identified any configuration or operational issues. Based on our findings, the delay appears to be related to the synchronization or communication between XCP-ng and CloudStack, resulting in slow propagation of VM state changes from XCP-ng to CloudStack.
We would appreciate your assistance in investigating the cause of this delay and identifying any configuration or performance-related factors that could be affecting the status update mechanism.
-
Hi,
XCP-ng got an event system that will propagate things like this instantly, at least that's the way it works normally
- Do you have the same behaviour in Xen Orchestra?
- Have you reported the issue to CloudStack?
- If you have an XCP-ng support subscription, you can also open a ticket so we can take a look on XCP-ng status to catch any obvious issue.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login