-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 3.4.20
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-08-26
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
As part of rolling index builds and similar operations, we'll often take nodes offline for O(hours). When the node comes back online, we'll put it into maintenance mode (using replSetMaintenance) until the node catches back up. We've observed that such nodes often end up with a huge WiredTigerLAS.wt file. We've done some investigation and it seems to be the case that this only happens when we put the node into maintenance mode; if we simply let a lagged node stay in secondary mode, we don't see WiredTigerLAS.wt grow.
We suspect this is related to cache pressure of majority read concern since we only started seeing these issues when we enabled that.
- is related to
-
-
- Closed
-
-
SERVER-19209 Need to drop all storage snapshots on rs resync
-
- Closed
-
-
SERVER-18022 Support "read committed" isolation level where "committed" means confirmed by the voting majority of a replica set
-
- Closed
-