The ReplBatcher has been identified as an actor that keeps a long-running OperationContext. This can cause problems such as WT table drops to fail until the OperationContext is destroyed.
- is related to
SERVER-22766 Dynamic oplog sizing for WiredTiger nodes
SERVER-31654 ReplBatcher should recalculate batch limits after oplog is resized via replSetResizeOplog
- related to
SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext