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

$sort stage in aggregation doesn't call scoped connections done ()

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      sh.enableSharding("test")
      sh.shardCollection("test.shard",

      { _id : "hashed" }

      )
      db.shard.aggregate({$match:{ a:1 }}, {$sort: {_id:1}}, {$group:{_id:"$a"}})
      Check the logs of the database's primary shard for scoped connections being dropped.

      Show
      sh.enableSharding("test") sh.shardCollection("test.shard", { _id : "hashed" } ) db.shard.aggregate({$match:{ a:1 }}, {$sort: {_id:1}}, {$group:{_id:"$a"}}) Check the logs of the database's primary shard for scoped connections being dropped.
    • Sprint:
      Quint Iteration 7

      Description

      The sort stage doesn't properly close the connection. This causes it to be marked as bad and not returned to the pool which leads to many log lines and connection churn. Potentially gigs per hour of log lines on a small cluster.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: