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

Print write conflict log at logWriteConflictAndBackoff () in production build

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • v8.0
    • Repl 2024-07-08, Repl 2024-07-22
    • 200

      I am looking at https://jira.mongodb.org/browse/BF-33674. Here jstests/concurrency/fsm_workloads/analyze_shard_key.js test is failing with Hang analyzer killing it after timeout. Issue here is, At recovery time, while applying commitTransaction oplog, it is hitting write conflict continuously until it get resolved. Currently When write conflict happens we increment the number of attempts in logWriteConflictAndBackoff() and keep retrying. When it hits 10k limit we print the log only in case of debug build. In the production build, we don't print any log. Isn't it good idea to print some log even in case of production build with same or higher limit? Otherwise there is no way to find this issue in production build.

            Assignee:
            kishore.devireddy@mongodb.com Kishore Devireddy
            Reporter:
            kishore.devireddy@mongodb.com Kishore Devireddy
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: