[SERVER-59575] fix log ID in TimestampMonitor Created: 25/Aug/21  Updated: 29/Oct/23  Resolved: 28/Aug/21

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Trivial - P5
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-59639 re-enable the use of regex in errorco... Closed
is related to SERVER-58025 TimestampMonitor listener loop crashe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-09-06
Participants:

 Description   

The log ID in the exception handler for the TimestampMonitor should be 5802500 instead of 58025 per log system convention.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 28/Aug/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-59575 SERVER-59639 re-enable regex in errorcodes.py

This reverts commit 5b78474fa9d0df4aaeab73f4384d3ab8a026dac8.
Branch: master
https://github.com/mongodb/mongo/commit/7d155b747d0e867a10644b69093cd1f9bc809bc2

Comment by Githook User [ 27/Aug/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-59575 temporarily disable the use of regex in errorcodes.py
Branch: master
https://github.com/mongodb/mongo/commit/5b78474fa9d0df4aaeab73f4384d3ab8a026dac8

Comment by Githook User [ 26/Aug/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-59575 fix log ID in TimestampMonitor
Branch: master
https://github.com/mongodb/mongo/commit/42b582036830e22d40195ee0ff2904ab0d883e6a

Generated at Thu Feb 08 05:47:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.