Confirm that you are experiencing this issue before attempting to complete the steps outlined in the resolution below.
To confirm that you are experiencing this issue:
- Open a browser window and go to https://vCenter_Server/VOD/index.html.
- In Detail Pages, click Pull Counters.
- Look for the string Evictions and check to see if any counters are non-zero.
Note: There are approximately 14 categories of Evictions. Look for all occurrences of Evictions and ensure that all instances of .../Evictions/Count/total are at zero. These lines are spread throughout the pull counters page, rather than appearing in one big group as shown here.
If you are hitting this issue, the counters are non-zero:
/InventoryStats/VpxdCache/Nmspc='resConfig'/Evictions/Count/total 19568
/InventoryStats/VpxdCache/Nmspc='vmconfig'/Evictions/Count/total 3569418
If you are not hitting this issue, the counters are zero:
/InventoryStats/VpxdCache/Nmspc='resConfig'/Evictions/Count/total 0
/InventoryStats/VpxdCache/Nmspc='vmconfig'/Evictions/Count/total 0
To resolve this issue:
- Log into the vSphere Client.
- Go to Administration > vCenter Server Settings > Advanced Settings > VirtualCenter.CacheSize.
- Change the value to 9223372036854775807 (unlimited).
- You can also verify that this value is set by looking for this entry in the vpxd-profiler-#.log. However, instead of showing the above value for unlimited, the profiler logs will show a value of -1.
/InventoryStats/VpxdCache/Capacity/total -1
- In the task manager, the vpxd.exe process shows a drop in CPU utilization almost immediately.
Note:
- This value can be changed without a VirtualCenter restart.
- When you change this parameter, the vpxd memory utilization may increase.
- Even though the CPU utilization shows a drop almost immediately, these counters do not automatically go to zero after you apply the changed value. Instead, they stop increasing. If you restart the vCenter Server service, they drop down to zero.