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

Open cursors can block cleanupOrphaned

    • Type: Icon: Question Question
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.2
    • Component/s: Sharding
    • None

      We run a sharded cluster. When trying to run cleanupOrphaned on some of those, the primary instance only logs the following:

      2020-08-06T08:19:03.481+0000 I SHARDING [conn25449020] Deletion of XXX range [{ _id: MinKey }, { _id: -XXXXXXXX }) will be scheduled after all possibly dependent queries finish

       

      We verified that no other operations are running on this shard with the following query:

      {{ db.currentOp().inprog.map(function (o) { if (o.ns === "admin.$cmd") return

      { opid: o.opid, secs: o.secs_running, ns: o.ns, command: o.command }

      }).filter(Boolean)}}

      Even after waiting for over an hour (the normal timeout for cleanupOrphaned) there is no feedback whatsoever.
      {{Is there anything we can do to successfully clean orphaned documents from the affected shards? }}

      Thank you.

            Assignee:
            eric.sedor@mongodb.com Eric Sedor
            Reporter:
            leo@jodel.com Leo Be
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: