The MissingLoc structure already tracks locations of any missing object
on any acting OSD, and is updated on_local_recover and on_global_recover.
Update it on_peer_recover too so that the loc information (and derivative
missing_by_count info) is correct.
Signed-off-by: Sage Weil <sage@redhat.com>
publish_stats_to_osd();
// done!
peer_missing[peer].got(soid, recovery_info.version);
+ missing_loc.add_location(soid, peer);
}
void PrimaryLogPG::begin_peer_recover(