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

when one shard goes down, mongos starts returning failure in getlasterror for all the shards, to already connected client.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 1.8.1
    • Fix Version/s: 2.0.3, 2.1.0
    • Component/s: Sharding
    • Labels:
      None
    • Environment:
      Mongo version 1.8.1 on 64-bit Debian machine
    • Operating System:
      Linux

      Description

      MongoDB with 2 shards. When both the shards are up and running, our mongo driver using MongoS
      inserts the objects properly and get proper codes in getLastError.
      When one of the shard(Shard1) is down (MongoD process is crashed), MongoS
      starts giving socket exception (with code *) for both shards. (Even though
      it keeps inserting objects on one shard2)

      At the same time if another mongo driver tries to connect to same MongoS, it
      gives proper codes in getLastError i.e. for shard1 it gives socket exception
      and for shard2 it gives success. (Also if we stop and start our application
      again it works properly)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              milkie Eric Milkie
              Reporter:
              anurag.berdia anurag berdia
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: