PRIMARY down on sharded cluster - downtime

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.12, 2.6.5
    • Component/s: Sharding
    • None
    • ALL
    • Hide

      I can replicate this behaviour when running mongos on top of single replicaset (PRIMARY, SECONDARY, ARBITER), then I run simple ruby script (https://gist.github.com/lowang/5fc24c6e40b03a613d2b - using original mongo gem, with secondary_preferred) issuing 2 read queries per second to sharded collection.
      Then I simulate PRIMARY server problem by issuing "halt -n -f" on it's virtual machine. After few seconds script cannot get results.

      Show
      I can replicate this behaviour when running mongos on top of single replicaset (PRIMARY, SECONDARY, ARBITER), then I run simple ruby script ( https://gist.github.com/lowang/5fc24c6e40b03a613d2b - using original mongo gem, with secondary_preferred) issuing 2 read queries per second to sharded collection. Then I simulate PRIMARY server problem by issuing "halt -n -f" on it's virtual machine. After few seconds script cannot get results.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I've got downtime (read queries cannot complete) when PRIMARY is down in sharded cluster.
      It takes from about 20-30s (original mongo gem),
      however original mongo gem is not a problem as I can't issue a query during that time while connecting to mongos directly with mongo client.
      Upgrading to mongo 2.6 didn't improve downtime at all.

        1. logs
          79 kB
          Ramon Fernandez

            Assignee:
            Ramon Fernandez
            Reporter:
            Przemek Wroblewski
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: