For as long as I can remember on my HV 5.3 install, the vCenter logs have been filled with RecomputeDigests events. I have had to dial down the retention periods to 1 day to keep the vCenter DBs from filling. I only have about 100 VMs so I am stumped as to why it insists on recomputing so often. I have been unable to find any similar posts on this problem. We're running Horizon View 5.3 on ESXi 5.5.0 with all current patches. There are no 3rd party storage accelerators or other add-ons. Any ideas where to look?
Here's a typical entry in the view debug log...
2014-11-30T07:33:06.353-06:00 DEBUG (08D8-0E98) <HAResourceManager> [PendingOperationSet] com.vmware.vdi.desktopcontroller.VirtualCenterDriver@4795949e Received Prepare from MNJView2F for RecomputeDigests on /MNJ5/vm/Discovered virtual machine/MNJ-Assigned-Pool-1/kboerner-vdt(vm-615)
2014-11-30T07:33:06.354-06:00 DEBUG (08D8-0E98) <HAResourceManager> [VirtualCenterDriver] Accepting Prepare from MNJView2F for RecomputeDigests on /MNJ5/vm/Discovered virtual machine/MNJ-Assigned-Pool-1/kboerner-vdt(vm-615)
2014-11-30T07:33:06.357-06:00 DEBUG (08D8-0E98) <HAResourceManager> [PendingOperationSet] com.vmware.vdi.desktopcontroller.VirtualCenterDriver@4795949e Received Prepare from MNJView2F for RecomputeDigests on /MNJ5/vm/Discovered virtual machine/MNJ-Assigned-Pool-1/kcowan-vdt(vm-407)
2014-11-30T07:33:06.358-06:00 DEBUG (08D8-0E98) <HAResourceManager> [VirtualCenterDriver] Accepting Prepare from MNJView2F for RecomputeDigests on /MNJ5/vm/Discovered virtual machine/MNJ-Assigned-Pool-1/kcowan-vdt(vm-407)
.
.
.