[SERVER-25071] Ensure replication batch finishes before shutdown - MongoDB Jira

XML

Word

Printable

Much like ~~SERVER-24933~~, we should ensure that our shutdown lands between apply batches.

There are a few ways to get there:

Ignore shutdown interruptions during apply batch (not good for long running applies like index builds)
Have shutdown wait for the current apply batch (similar to above)
Undo/reset current batch work on shutdown to be in a consistent state

In addition we should move setting the minvalid boundaries under the PBWM lock so that minvalid reflects the completed apply batch.

is documented by

DOCS-9468 Docs for SERVER-25071: Ensure replication batch finishes before shutdown

is duplicated by

SERVER-12528 SIGTERM can cause an fassert if we're actively replicating

is related to

SERVER-25248 minvalid should be set while appropriate locks are held

related to

SERVER-24933 Clean shutdown of secondaries should occur in between oplog batches, not during

SERVER-32935 improve exception handling in SyncTail::oplogApplication()

WT-2649 Some way to indicate valid points in the WT log

SERVER-7200 use oplog as op buffer on secondaries

(2 related to)

Participants:: Andy Schwerin, Githook User, Kevin Pulo, Mathias Stearn, Scott Hernandez