[SERVER-59823] wiredTigerPrepareConflictRetry should log prepare conflicts in log-level 1, not only in debug builds Created: 07/Sep/21  Updated: 27/Oct/23  Resolved: 13/Sep/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.0, 5.0.2
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45869 automatically convert structured logg... Closed
Sprint: Execution Team 2021-09-20
Participants:

 Description   

I was interested in WT_PREPARE_CONFLICT logging in regards to a customer HELP ticket. It looks like we changed the logging from log-level 1 to debug build logging in SERVER-45869, which seems suspicious because that was an automatic conversion.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 13/Sep/21 ]

I interpreted this incorrectly. LOGV2_DEBUG doesn't mean debug build only, it's just the new naming for any logs not always logged. Log-level 1 will still print this message, as before.

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