In certain cases, the beacon was emitted from within
handle_mds_map (via MDCache::rejoin_start and
the "No subtrees found for root MDS rank!" error
handler. This was happening before Beacon::notify_mdsmap
had been called with the new epoch, so the DAMAGED
beacon had the old epoch set, and was consequently
ignored by the MDSMonitor.
The symptom would be that MDS ranks with metadata damaged
in this particular way would flap instead of gracefully
going damaged.