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
- related to
SERVER-36159 Log whenever the gossiped config server opTime term changes