Unable to Disable Performance Service in vSAN 8/9
Article ID: 312585
Updated On:
Products
Issue/Introduction
As of vSAN version 8 and higher, the disable option for vSAN Performance Service has been removed from the vCenter Web Client.
This article describes steps on how to disable vSAN Performance Service as part of troubleshooting issues with vSAN Performance Service.
Environment
VMware vSAN 9.x
Resolution
Follow below steps to disable Performance Service:
1 Log in vCSA from ssh client or vCSA VM Console.
2 Enable vCSA shell access and log in rvc with sso administrator user.
3 From rvc, run "vsan.perf.stats_object_info" under /localhost/Datacenter/computers> to query vSAN Performance Service related Object information for specific vSAN Cluster:
/localhost/Datacenter/computers> vsan.perf.stats_object_info 0
Directory Name: .vsan.stats
vSAN Object UUID: 01e0f764-####-####-####-#########7d
SPBM Profile: vSAN Default Storage Policy
vSAN Policy: hostFailuresToTolerate: 1, cacheReservation: 0, stripeWidth: 1, proportionalCapacity: 0, forceProvisioning: 0, iopsLimit: 0, checksumDisabled: 0, subFailuresToTolerate: 0, spbmProfileGenerationNumber: 0, spbmProfileId: aa6d5a82-####-####-####-#########ad, compressionDisabled: 0
vSAN Object Health: healthy
DOM Object: 01e0f764-####-####-####-#########7d (v17, owner: esxi1.example.com, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = [0, 100], hostFailuresToTolerate = 1, forceProvisioning = 0, spbmProfileId = aa6d5a82-####-####-####-#########ad, spbmProfileGenerationNumber = 0, CSN = 2, spbmProfileName = vSAN Default Storage Policy)
RAID_1
Component: 01e0f764-####-####-####-#########7d (state: ACTIVE (5), host: esxi1.example.com, capacity: mpx.vmhba3:C0:T0:L0, cache: mpx.vmhba2:C0:T0:L0,
votes: 1, usage: 0.2 GB, proxy component: false)
Component: 01e0f764-####-####-####-#########7d (state: ACTIVE (5), host: esxi2.example.com, capacity: mpx.vmhba1:C0:T0:L0, cache: mpx.vmhba2:C0:T0:L0,
votes: 1, usage: 0.2 GB, proxy component: false)
Witness: 01e0f764-####-####-####-#########7d (state: ACTIVE (5), host: esxi3.example.com, capacity: mpx.vmhba1:C0:T0:L0, cache: mpx.vmhba2:C0:T0:L0,
votes: 1, usage: 0.0 GB, proxy component: false)
Extended attributes:
Address space: 273804165120B (255.00 GB)
Object class: vmnamespace
Object path: /vmfs/volumes/vsan:52a9537793######-c08e3f91e6######/.vsan.stats
Object capabilities: NONE
4 Use "vsan.perf.stats_object_delete" to delete vSAN Performance Service object:
/localhost/Datacenter/computers> vsan.perf.stats_object_delete 0
Deleting vSAN Stats DB object, which will stop vSAN Performance Service ...
Task: Disable vSAN performance service
New progress: 1%
New progress: 50%
Task result: success
5 Monitor Recent Task from vSphere Client， there will be a task name “Disable vSAN Performance Service”：
6 After the “Disable vSAN Performance Service” task completed, check Performance Service status again, it will show "Disabled" status:
Note: If you are unfamiliar with using RVC (Ruby vSphere Console), please refer to KB Ruby vSphere Console (RVC)
If the standard RVC command (vsan.perf.stats_object_delete) or the vCenter UI fails to delete the object, it usually means the object is in a "Missing" or unhealthy state.
When this happens, vCenter's API calls to disable the service will hang or time out because it cannot read the object properly to delete it from the vSAN datastore.
If you are still having an issue, please contact vSAN Support for assistance.
Feedback
