-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.3.0
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2016-08-29
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 duplicated by
-
SERVER-12528 SIGTERM can cause an fassert if we're actively replicating
- Closed
- is related to
-
SERVER-25248 minvalid should be set while appropriate locks are held
- Closed
- related to
-
SERVER-24933 Clean shutdown of secondaries should occur in between oplog batches, not during
- Closed
-
SERVER-32935 improve exception handling in SyncTail::oplogApplication()
- Closed
-
WT-2649 Some way to indicate valid points in the WT log
- Closed
-
SERVER-7200 use oplog as op buffer on secondaries
- Closed