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

MongoDB secondary member exception status with error 'replSet source for syncing doesn't seem to be await capable'

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical - P2 Critical - P2
    • None
    • None
    • None
    • None
    • ALL

    Description

      Background:

      1) I installed below 2 rpm packages on CentOS 6.3(Final) 64bits
      mongo-10gen-2.2.1-mongodb_1.x86_64.rpm
      mongo-10gen-server-2.2.1-mongodb_1.x86_64.rpm
      2) A replicate Set deploy as followings:
      Machine1:one primary,one arbiter
      Machine2:one secondary
      Set a shard cluster for this replicate set
      3) The network interface of Machine 2(secondary member resided) has been outage for some reason for 2 days(This is likely to casue the machine2 to lose communction with others members). Then I fixed the network issue later.

      Symptom:

      When run rs.status() on mongo primary, find secondary exception status with error message 'db exception in producer: 1000 replSet source for syncing doesn't seem to be await capable – is it an older version of mongodb?'

      Dump message for details: rs1:PRIMARY> rs.status()
      {
      "set" : "rs1",
      "date" : ISODate("2013-07-08T10:25:31Z"),
      "myState" : 1,
      "members" : [

      { "_id" : 0, "name" : "app1_ss_nc:27017", "health" : 1, "state" : 2, "stateStr" : "SECONDARY", "uptime" : 2151, "optime" : Timestamp(1372928780000, 2), "optimeDate" : ISODate("2013-07-04T09:06:20Z"), "lastHeartbeat" : ISODate("2013-07-08T10:25:30Z"), "pingMs" : 0, // error "errmsg" : "db exception in producer: 1000 replSet source for syncing doesn't seem to be await capable -- is it an older version of mongodb?" }

      ,

      { "_id" : 1, "name" : "app2_ss_nc:27017", "health" : 1, "state" : 1, "stateStr" : "PRIMARY", "uptime" : 10543, "optime" : Timestamp(1373277727000, 1), "optimeDate" : ISODate("2013-07-08T10:02:07Z"), "self" : true }

      ,

      { "_id" : 2, "name" : "storage_ss_nc:27027", "health" : 1, "state" : 7, "stateStr" : "ARBITER", "uptime" : 2409, "lastHeartbeat" : ISODate("2013-07-08T10:25:30Z"), "pingMs" : 0 }

      ],
      "ok" : 1
      }

      How can I fix this problem?

      Attachments

        Activity

          People

            Unassigned Unassigned
            jameszhou jameszhou
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: