* filer: stop following a peer that stays unreachable
* filer: re-track an answering peer only while it is still followed
A signature read that succeeds just before the master removes the peer
called initPeerWatermark after the removal, clearing its mark. The loop
then exits, so the watermark it re-tracked never advances or drops and
pins aggregated readers at the settled horizon.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: forget a peer's unreachable clock when the master removes it
Only a successful connection cleared the clock, so every departed address
that once failed stayed in the map for the filer's lifetime, and a re-added
peer inherited the old outage. The removal now drops it, and the clock is
guarded by peerChansLock so the removed peer's exiting loop cannot start a
new one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: report the unreachable mark only when it is set
Once peerResumeRetention forgets the mark of a peer that stays
unreachable, markPeerWatermarkRemoved no longer marks it (its watermarks
are gone), but notePeerUnreachable still saw no mark and logged
"treating it as removed" on every retry. markPeerWatermarkRemoved now
reports whether it set a new mark.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: fix the unreachable-peer subscriber's start before the baseline write
The subscriber goroutine picked its start time itself, so a baseline write
that finished first fell before the subscription and the test failed after
20 seconds with correct delivery.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>