vSAN Health Service - Stretched cluster – Shared witness per cluster component limit scaled down
Article ID: 317667
Updated On:
Products
VMware vSAN
Issue/Introduction
This article explains the stretched cluster - Shared witness per cluster component limit scaled down check in the vSAN Health Service and provides details on why it reports an issue.
Resolution
Q: What does the stretched cluster - Shared witness per cluster component limit scaled down check do?
Shared witness feature allows multiple ROBO clusters attaching to one shared witness host. On shared witness host there is a per cluster component limit which controls how many components each cluster can create. According to memory resource constraint, the per cluster component limit number would be scaled down if memory is insufficient. This health check will verify whether per cluster component limit is scaled down.
Q: What does it mean if it shows an error state?
The maximum supported per cluster component number on the shared witness host doesn't satisfy the required number due to insufficient memory.
Q: How to fix the error state?
Add more memory resource to the shared witness host.
Shared witness feature allows multiple ROBO clusters attaching to one shared witness host. On shared witness host there is a per cluster component limit which controls how many components each cluster can create. According to memory resource constraint, the per cluster component limit number would be scaled down if memory is insufficient. This health check will verify whether per cluster component limit is scaled down.
Q: What does it mean if it shows an error state?
The maximum supported per cluster component number on the shared witness host doesn't satisfy the required number due to insufficient memory.
Q: How to fix the error state?
Add more memory resource to the shared witness host.
Feedback
Yes
No
Powered by
