Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42155

Indicate term mismatches when readConcern times out

    XMLWordPrintable

    Details

    • 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:

      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.

        Attachments

          Issue Links

          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-36159 Log whenever the gossiped config server opTime term changes

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: