I wanted to come back and revisit this as we might have this resolved, for now. I installed the vSAN hotfix (2.0.0.7192536) for our Large environments. Actually, all of our vROPs clusters are Large environments, but we do have some vSAN adapters with 200-900 objects.
Along with the hotfix above, I also put in some workarounds that were suggested by VMware engineering: We made changes to the below file
File: /usr/lib/vmware-vcops/user/plugins/inbound/VirtualAndPhysicalSANAdapter3/conf/config.properties
Original File:
# Frequency the resource collection should take place
RESOURCE_DISCOVERY_FREQUENCY = 5
# vCenter resources cache update frequency
VCENTER_RESOURCE_DISCOVERY_FREQUENCY = 5
# Pool sizes for discovery & collection
DISCOVERY_POOL_SIZE = 3
COLLECTION_POOL_SIZE = 5
# VIM Client read timeout (ms)
VIMCLIENT_READ_TIMEOUT = 120000
Edited File:
# Frequency the resource collection should take place
RESOURCE_DISCOVERY_FREQUENCY = 5
# vCenter resources cache update frequency
VCENTER_RESOURCE_DISCOVERY_FREQUENCY = 5
# Pool sizes for discovery & collection
DISCOVERY_POOL_SIZE = 3
COLLECTION_POOL_SIZE = 5
# VIM Client read timeout (ms)
# VIMCLIENT_READ_TIMEOUT = 120000
# VMWARE WORKAROUNDS TO VSAN BUG
CIM_SERVICE_PROTOCOL = none
VIMCLIENT_READ_TIMEOUT = 900000
I have this now installed in 2 cluster which were seeing the "Old Data Receiving" issue. I can now say that we seem to be receiving metrics, although, some of the vSAN metrics seem to be 20 mins behind, which I would expect since we increased the READ_TIMEOUT. I will wait for the weekend to pull a full log bundle to confirm the cluster is not seeing the errors pertaining to the vSAN bug.
I hope everyone else who was affected has this resolved now. I am looking forward to the new vROps release with fixes.