50s failure of local log follower node lead to write unavailability

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • ALL
    • Hide

      Raise the priority to P2 as it's blocking https://jira.mongodb.org/browse/SERVER-112964

      Show
      Raise the priority to P2 as it's blocking https://jira.mongodb.org/browse/SERVER-112964
    • SESIPowerPlay - 2026-03-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Insert 20 took ~29 seconds, this happened after local log follower had been down about 30s. Write immediately stopped almost right after the pod was deleted.diagnostic.data.tar

      [2026-02-24T18:49:08.883Z] Insert 19: 81ms - ID: 699df2a4eda528820f48f290
      [2026-02-24T18:49:38.992Z] Insert 20: 29108ms - ID: 699df2a5eda528820f48f291
      [2026-02-24T18:49:40.079Z] Insert 21: 86ms - ID: 699df2c3eda528820f48f292

      mongod version: a4d82907441f0d11596be3f4ce4809daf0c9849f
      sls version: d2d1c0ee61e3425928a2cf26694af411c1b23974

        1. diagnostic.data.tar
          734 kB
          Daotang Yang
        2. mongod.log
          16.44 MB
          Daotang Yang

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

              Created:
              Updated:
              Resolved: