-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Minor Change
-
v4.2, v4.0, v3.6, v3.4
-
Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-09-09
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We should extend the error message returned as part of the WriteConcernError (or the ExceededTimeLimit error) to include text like: "Current term is 1 but request is asking for 6" or something similar. This would help alert users that a mismatches/unsatisfiable term is causing the error.
The second half of work previously tracked on SERVER-36159.
- related to
-
SERVER-36159 Log whenever the gossiped config server opTime term changes
-
- Closed
-