Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.15, 4.0.13, 4.2.1, 4.3.1
Affects Version/s: None
Component/s: Replication, Sharding
Labels:
None

Backwards Compatibility:
Minor Change
Backport Requested:

v4.2, v4.0, v3.6, v3.4
Sprint:
Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-09-09
Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

Assignee:: Kevin Pulo
Reporter:: Kevin Pulo
Participants:: Githook User, Kevin Pulo
Votes:: 1 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Jul 11 2019 05:45:54 AM UTC
Updated:: Oct 29 2023 10:19:11 PM UTC
Resolved:: Sep 02 2019 05:50:39 AM UTC
Confidence Status Last Update:: 11/Jul/19 5:48 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates