50s failure of remote log leader leads to write unavailability

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • ALL
    • SESIPowerPlay - 2026-03-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      About 10seconds

       58 [2026-02-23T21:39:15.375Z] Insert 58: 61ms - ID: 699cc9031b228e1a898080bd
       59 [2026-02-23T21:39:26.392Z] Insert 59: 10012ms - ID: 699cc9041b228e1a898080be
       60 [2026-02-23T21:39:27.474Z] Insert 60: 81ms - ID: 699cc90f1b228e1a898080bf

      diagnostic.data.tarmongod.log

       

      mongod version: a4d82907441f0d11596be3f4ce4809daf0c9849f
      sls version: d2d1c0ee61e3425928a2cf26694af411c1b23974

        1. diagnostic.data.tar
          246 kB
        2. mongod.log
          48.60 MB

            Assignee:
            Unassigned
            Reporter:
            Daotang Yang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: