[SERVER-42155] Indicate term mismatches when readConcern times out Created: 11/Jul/19  Updated: 29/Oct/23  Resolved: 02/Sep/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 3.6.15, 4.0.13, 4.2.1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-36159 Log whenever the gossiped config serv... Closed
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
Participants:
Case:

 Description   

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.



 Comments   
Comment by Githook User [ 16/Sep/19 ]

Author:

{'name': 'Kevin Pulo', 'username': 'devkev', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-42155 include relevant optimes in read concern timeout reporting

(cherry picked from commit e086820df23f95fd6f8ce5be6280bd5a791c7ec6)
Branch: v3.6
https://github.com/mongodb/mongo/commit/fd24abfe23e40b6a57bd82ee7bf54cccfe1d9048

Comment by Githook User [ 13/Sep/19 ]

Author:

{'username': 'devkev', 'email': 'kevin.pulo@mongodb.com', 'name': 'Kevin Pulo'}

Message: SERVER-42155 include relevant optimes in read concern timeout reporting

(cherry picked from commit e086820df23f95fd6f8ce5be6280bd5a791c7ec6)
Branch: v4.0
https://github.com/mongodb/mongo/commit/36d44f44226f79c9e3ec0a74f37dd9c340273771

Comment by Githook User [ 13/Sep/19 ]

Author:

{'name': 'Kevin Pulo', 'username': 'devkev', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-42155 include relevant optimes in read concern timeout reporting

(cherry picked from commit e086820df23f95fd6f8ce5be6280bd5a791c7ec6)
Branch: v4.2
https://github.com/mongodb/mongo/commit/bf9a3a3bd3055237b72d50d8f86b43420ea10d68

Comment by Githook User [ 02/Sep/19 ]

Author:

{'username': 'devkev', 'email': 'kevin.pulo@mongodb.com', 'name': 'Kevin Pulo'}

Message: SERVER-42155 include relevant optimes in read concern timeout reporting
Branch: master
https://github.com/mongodb/mongo/commit/e086820df23f95fd6f8ce5be6280bd5a791c7ec6

Generated at Thu Feb 08 04:59:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.