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

Receiving Rplicaset Error intermittently without explanation: Exception: Failed on findOne(): 16340 No replica set monitor active and no cached seed found for set: rs5

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker - P1 Blocker - P1
    • None
    • 2.2.0
    • Internal Client
    • None
    • PRODUCTION

    Description

      Hi,
      We have 6 replicasets used in our production environment and we are seeing at odd times the following error in our application logs

      Exception: Failed on findOne(): 16340 No replica set monitor active and no
      cached seed found for set: rs5

      I can't find a reference to this error code or message, so putting in a ticket hoping someone can help us understand what happens. This usually fails and recovers 10-20 minutes later.

      When this happens, we check and the replica set is alive and healthy.

      We are using the c++ driver and using mongo 2.2

      Attachments

        Activity

          People

            william.zola@10gen.com William Zola
            warren@everyscreenmedia.com Warren Chang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: