In SERVER-62921, we added more logging to isEligibleSyncSource/increased the verbosity so we always print the reason why we are not selecting a candidate as sync source. Since merging, we've received several HELP tickets about these logs and requests to reduce the frequency. 

We addressed the case of high frequency for ping time logging (SERVER-85915) and arbiter logging (SERVER-124981), but we are still receiving customer feedback about it, so we should consider re-evaluating this code path.these logs to see if they are serving the intended observability purpose or should be changed/lowered to debug level.

We should also re-evaluate why arbiters need to go through sync source evaluation as part of their steady state behavior. They do not ever maintain sync sources, so this is misleading and may be unnecessary extra work, especially since it actually gets blocked from syncing at a higher level in prepareSyncFromResponse which is called in ReplicationCoordinatorImpl::processReplSetSyncFrom.