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

MongoS connections that persist across an upgrade become stale and can cause subsequent operations to fail

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • ALL

    Description

      After an upgrade of a sharded cluster, the MongoS' connections to the newly-restarted MongoDs are stale. If subsequent operations are performed before the stale connections are flushed from the pool, then the operations can fail.

      The attached test case works because it sleeps for 5 seconds after the upgrade (allowing some stale connections to be reaped), and then retries connecting to run its count() operation. If the retry wrapper (the assert.soon()) is removed, the count() fails because the first connection it uses is still stale.

      Attachments

        Activity

          People

            greg_10gen Greg Studer
            sam.helman@10gen.com sam.helman@10gen.com
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: