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

Various errors seen when one node dies in a shard.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • 1.8.0
    • Sharding
    • None
    • Linux x86_64
    • ALL

    Description

      Repro:

      1. Set up two shards, each with one primary, one secondary, and one arbiter.
      2. Enable sharding on a database.
      3. Shard a collection in the database.
      4. Insert enough documents to distribute them between the shards.
      5. Run a test that constantly runs various queries against the collection.
      6. While running the test kill a random mongod then restart it.

      After killing the mongod you may or may not see errors like this:

      database error: DBClientBase::findOne: transport error: ...
      database error: socket exception
      database error: dbclient error communicating with server: ...

      These errors are passed back to the client application by mongos. Is this the expected behavior?

      This was found while trying to reproduce PYTHON-212.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bernie@mongodb.com Bernie Hackett
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: