return no data when slaves are down

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.3
    • Component/s: Cluster Management
    • None
    • Environment:
      linux
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Two of secondary nodes are out of sync. However, the primary has the latest data.

      > rs.status()
      {
      "set" : "lp",
      "date" : "Fri Nov 19 2010 15:54:38 GMT-0800 (PST)",
      "myState" : 1,
      "members" : [

      { "_id" : 0, "name" : "stage1.vpc3.estalea.net:4101", "health" : 1, "state" : 1, "self" : true }

      ,

      { "_id" : 1, "name" : "stage1.vpc3.estalea.net:4102", "health" : 1, "state" : 2, "uptime" : 3653, "lastHeartbeat" : "Fri Nov 19 2010 15:54:37 GMT-0800 (PST)", "errmsg" : "error RS102 too stale to catch up" }

      ,

      { "_id" : 2, "name" : "stage1.vpc3.estalea.net:4103", "health" : 1, "state" : 2, "uptime" : 3651, "lastHeartbeat" : "Fri Nov 19 2010 15:54:37 GMT-0800 (PST)", "errmsg" : "error RS102 too stale to catch up" }

      cur = coll.find(dbQuery).addOption(
      Bytes.QUERYOPTION_SLAVEOK);

      return no result.

            Assignee:
            Scott Hernandez (Inactive)
            Reporter:
            Joseph Wang
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: