vSAN Health Service - Performance Service - Stats DB object conflicts check
Article ID: 317847
Updated On:
Products
VMware vSAN
Issue/Introduction
This article explains the Performance Service - ‘Stats DB object conflicts’ check in the vSAN Health Service and provides details about why it might report an error.
Environment
VMware vSAN (All Versions)
Resolution
Q: What does the Performance Service - Stats DB object conflicts check do?
A: The check verifies if there are multiple Stats DB objects.
Q: What does it mean when it is in an error state and how do i troubleshoot the issue?
A: Multiple Stats DB objects can be found in the cluster. The one in use might not be the one with the most relevant history. This can happen after a cluster merge. If the other Stats DB objects are no longer useful, then the datastore browser can be used to delete the additional renamed directories. The renamed directories, such as ".vsan.stats (1)" are shown in the health check results. You can find the renamed directory in the root directory of the vSAN datastore.
If the other Stats DB objects are useful, they can be backed up as files through the datastore browser, or they can be renamed and kept in the datastore. Merging of multiple Stats DB objects is not supported.
Screenshots showing the delete process with the datastore browser:
Confirm the error in Skyline Health:
A: The check verifies if there are multiple Stats DB objects.
Q: What does it mean when it is in an error state and how do i troubleshoot the issue?
A: Multiple Stats DB objects can be found in the cluster. The one in use might not be the one with the most relevant history. This can happen after a cluster merge. If the other Stats DB objects are no longer useful, then the datastore browser can be used to delete the additional renamed directories. The renamed directories, such as ".vsan.stats (1)" are shown in the health check results. You can find the renamed directory in the root directory of the vSAN datastore.
If the other Stats DB objects are useful, they can be backed up as files through the datastore browser, or they can be renamed and kept in the datastore. Merging of multiple Stats DB objects is not supported.
Screenshots showing the delete process with the datastore browser:
Confirm the error in Skyline Health:
Find the renamed object folders in the datastore browser:
Delete the renamed object folders:
Additional Information
7.x there is an option in vCenter UI to disable and then re-enable the Performance Service.
In 8.x
The service has to be stopped with RVC tool from the vCenter CLI.
- Log into RVC via vCenter SSH.
- Open vCenter SSH.
- Log into shell
- Run the command:
rvc - Login with
administrator@<domain>@localhost
- cd into localhost > datacenter > computers > vSAN Cluster
- Then run the command to delete the vSAN performance object:
vsan.perf.stats_object_delete . - Once deleted, proceed to create the vSAN performance object by using the command:
vsan.perf.stats_object_create .
Note: You can also re-enable Performance Service via the vCenter Web Client.
- vSAN Health Service - Performance Service - Performance data collection check
- vSAN Health Service - Performance Service - Stats DB object check
- vSAN Health Service - Performance Service - Stats master election check
- vSAN Health Service - performance service - All hosts contributing stats check
- vSAN Health Service - Performance Service - Status Check
- vSAN Health Service - Performance service - Network diagnostic mode
- "Hosts with connectivity issues" or "All hosts contributing stats." warning after upgrading vSAN to 8.0U2
Feedback
Yes
No
Powered by
