Suppose you had a 3-node set, X, Y, Z, where X is primary, Y is
|
secondary, and Z is an arbiter. Y is a week behind, about to go
|
stale. Then X goes down, so Y becomes primary for a few minutes and
|
does some writes. Then X comes back up. Should X rollback a week's
|
worth of data automatically? The 300mb should probably be a bit more
|
of an advanced measure, but it's there to prevent that type of
|
thing.
|
|
I agree that having it endlessly loop on failure is a bad idea. It
|
should just exit or do something smarter.
|
|
I don't see how it could be a symptom of how you shut it down, it's
|
caused by a lot of data not being written to the secondary. Which
|
means the secondary was behind.
|