[SERVER-36730] Correct error codes to be consistent with 4.0.1 Created: 17/Aug/18  Updated: 29/Oct/23  Resolved: 21/Aug/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.1.1
Fix Version/s: 4.1.3

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Operating System: ALL
Sprint: Sharding 2018-08-27
Participants:

 Description   
  1. A backport to 4.0 renumbered the named error code TooManyLogicalSessions to 261 and ExceededTimeLimit to 262, which is not consistent with master. We should correct master so it is consistent with v4.0 and renumber all conflicting error codes.


 Comments   
Comment by Janna Golden [ 21/Aug/18 ]

To make master compatible with 4.0.1, we changed the following error codes such that they are now:
TooManyLogicalSessions: 261
ExceededTimeLimit: 262
TooManyFilesOpen: 264
FailPointSetFailed: 266

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-36730 Correct error codes to be consistent with 4.0.1
Branch: master
https://github.com/mongodb/mongo/commit/8a38c643f39e8f6a7afcd888a85f09800e3de2a1

Comment by Louis Williams [ 17/Aug/18 ]

greg.mckeon Because we have already released 4.0 with the wrong error codes, we can just change master to match 4.0 so that the error codes on 4.0 are no longer "wrong".

Comment by Gregory McKeon (Inactive) [ 17/Aug/18 ]

louis.williams should we be renumbering master to match 4.0, or 4.0 to match master? It seems to me if we add an error code to master and backport, it should take on the value in master.

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