-
Type:
Task
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Sharding 2018-05-07, Sharding 2018-06-04
-
None
-
None
-
None
-
None
-
None
-
None
-
None
If possible, it would be an improvement to eliminate the need to crash the entire server if the shard identity document is rolled back, if the appropriate in-memory state can be refreshed or invalidated. This may require a bit of investigation/discussion.