-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Minor Change
-
v4.2
-
Sharding 2019-07-01
We stopped using these fields in 3.6, but we still parse the minOpTime recovery document expecting to find them, returning a bad status if we can't. In 4.0, we stopped parsing these fields, but continued to write them, so when downgrading, a 3.6 node won't crash during sharding state recovery. After 4.0 ships, we can stop writing these fields.
- is related to
-
SERVER-25276 Remove code for parsing and handling config server connection string during sharding state recovery
- Closed