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

"db config reload failed"

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.1.0
    • Affects Version/s: 1.8.3
    • Component/s: Stability
    • Labels:
      None
    • Environment:
      Three shards running 1.8.3 on Ubuntu in EC2
    • ALL

      We got a couple of hundred of these errors today before our application closed the connection to mongos and reconnected:

      Mongo::OperationFailure: db config reload failed!
      

      the only thing I can see in the mongos logs at the same time is this:

      Sat Sep  3 06:12:57 [conn1630] ns: fragments_20110831.exposure_fragments ClusteredCursor::query attempt: 0
      Sat Sep  3 06:13:01 [conn1630] ns: fragments_20110831.exposure_fragments ClusteredCursor::query attempt: 0
      Sat Sep  3 06:13:12 [conn1630] ns: fragments_20110831.exposure_fragments ClusteredCursor::query attempt: 0
      

      which doesn't look related, but we have approximately 19000 lines of that message in the mongos log, just in the first six hours of today.

            Assignee:
            greg_10gen Greg Studer
            Reporter:
            iconara Theo Hultberg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: