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

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

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • 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.
    • 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

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19553 Mongod shouldn't use sayPiggyBack to send KillCursor messages

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              mathias@mongodb.com Mathias Stearn
              charlie.page@10gen.com Charlie Page
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: