Symptoms:
- After successful vSAN Cluster shutdown and Restart the alert for Stats Primary Election is triggered.
- Under this health check, the Stats Primary is not visible, but the CMMDS primary is visible
- Stats object shows missing.
- All the objects are healthy and all the VMs can be Powered On.
Issue Validation:
Performance Stats object ".vsan.stats" exists but shows as missing even though all its components are active and the object is healthy:
Object UUID: xxxxxxxx-2ed5-xxxx-a4c8-xxxxxxafc016Version: 20Health: healthyOwner: xxxxxxxxesx006.xxxx.xxxxxxx.comSize: 512.00 GBUsed: 0.19 GBUsed 4K Blocks: 0.00 GBPolicy:stripeWidth: 1cacheReservation: 0proportionalCapacity: [0, 100]hostFailuresToTolerate: 2forceProvisioning: 0spbmProfileId: xxxxxxxx-73b1-xxxx-b072-xxxxxx272e5spbmProfileGenerationNumber: 1storageType: AllflashreplicaPreference: CapacityiopsLimit: 0checksumDisabled: 0CSN: 35SCSN: 38spbmProfileName: Management - Optimal Datastore Default Policy - RAID6 -----> Note: RAID5 or RAID6Configuration:ConcatenationRAID_1Component: xxxxxxxx-540f-xxxx-9cc7-xxxxxxafc016Component State: ACTIVE,Address Space(B): 273804165120 (255.00GB), Disk UUID: xxxxxxxx-1366-xxxx-6e13-xxxxxx8e4008, Disk Name: t10.NVMe_xxxxxxxxKYDMV_xxxxxxxxxxxxxxxx:2Votes: 2,Capacity Used(B): 13877248 (0.01GB), Physical Capacity Used(B): 13877248 (0.01GB), Total 4K Blocks Used(B): 0 (0.00GB), Host Name: xxxxxxxxesx006.xxxx.xxxxxxx.comComponent: xxxxxxxx-540f-xxxx-9cc7-xxxxxxafc016Component State: ACTIVE, Address Space(B): 205353123840 (191.25GB), Disk UUID: xxxxxxxx-6880-xxxx-0cb7-xxxxxx4dc3f4, Disk Name: t10.NVMe_xxxxxxxxKYDMV_xxxxxxxxxxxxxxxx:2Votes: 1,Capacity Used(B): 1547904 (0.00GB), Physical Capacity Used(B): 8650752 (0.01GB), Total 4K Blocks Used(B): 0 (0.00GB), Host Name: xxxxxxxxesx006.xxxx.xxxxxxx.comType: vmnamespacePath: /vmfs/volumes/vsan:xxxxxxxxxxxx78139-xxxxxxxx477ba664/.vsan.stats (Missing)Group UUID: xxxxxxxx-2ed5-xxxx-a4c8-xxxxxxafc016Directory Name: .vsan.stats
VMware vSAN 8.x
This is caused due to a race condition where vSAN attempts to reinitialize the .vsan.stats object while DOMPauseAllCCPs is still set to 1 as part of the Shutdown Cluster Wizard process before setting DOMPauseAllCCPs back to the default of 0 during cluster restart. This only happens when the object has either a RAID5 or RAID6 storage policy.
Broadcom Engineering is aware of this issue and they are working on a fix due in a future release.
Current Workaround available is to Delete and Recreate the stats object via RVC:
If the .vsan.stats folder still exists on the vSAN datastore follow the below steps.
vsan.perf.stats_object_info . via RVC/usr/lib/vmware/osfs/bin/objtool delete -u <object_uuid> -f against the object uuid from step 1Another option is set the vSAN Datastore storage policy to the vSAN Default Policy which is RAID1
If you need assistance with this process open a case with vSAN Support