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

Mongos to ignore "fsyncLock called when not locked" error

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      With SERVER-78150, mongos returns an "fsyncLock called when not locked" error if fsyncUnlock has been invoked on an unlocked shard. This error should ignored instead of reporting it to the user. This error is also reported by mongod. It will be better to keep the behaviors of both monogd and mongos in sync and have both the components ignore this error.

            Assignee:
            david.chen@mongodb.com David Chen (Inactive)
            Reporter:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: