After a server power failure, the administrator noticed the scheduled resyncing in the cluster monitor displays objects to be resynchronized under the pending category.
Why are there objects in this category?
After a server power failure, the administrator noticed the scheduled resyncing in the cluster monitor displays objects to be resynchronized under the pending category.
Why are there objects in this category?
Objects in the pending category indicate that the resynchronization process cannot proceed despite the delay timer having expired. This situation typically arises when there are too many objects to be synchronized, or if the system lacks sufficient resources to carry out the resynchronization processes immediately. Therefore, the presence of objects in the pending category suggests that there are too many objects to be synchronized, making this the correct answer.
D - to many objects to resyn
"Pending" implies the delay timer has already expired but that there are not enough resources available to re-sync those objects. The only valid choice left is D. Reference: https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-monitoring-troubleshooting/GUID-57D74904-A8C4-4F3B-8D2A-1017AA8EBA85.html Remaining number of objects to be resynchronized. You can classify scheduled resyncing into two categories: scheduled and pending. The scheduled category displays the objects that are not resyncing because the delay timer has not expired. Resynchronization of objects starts once the timer expires. The pending category displays the objects with the expired delay timer that cannot be resynchronized. This can be due to insufficient resources in the current cluster or the vSAN FTT policy set on the cluster not being met.
D. There are too many objects to be synchronized.
Answer D is correct. As detailed by kernelkraut, if it is marked "pending", that means the timer is expired, and the objects are yet to be synchronized.
A is correct: Scheduled resyncing Remaining number of objects to be resynchronized. You can classify scheduled resyncing into two categories: scheduled and pending. The scheduled category displays the objects that are not resyncing because the delay timer has not expired. Resynchronization of objects starts once the timer expires. The pending category displays the objects with the expired delay timer that cannot be resynchronized. This can be due to insufficient resources in the current cluster or the vSAN FTT policy set on the cluster not being met