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

uncaught exception in mapreduce causes mongod to terminate

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.1.0
    • Affects Version/s: None
    • Component/s: MapReduce
    • Labels:
      None
    • ALL

      Root cause:

      Tue Nov 15 08:00:21 [conn202500] ERROR: Uncaught std::exception: could not initialize cursor across all shards because : socket exception @ prod1/aboutmemng-m01.db.aol.com:27017,aboutmemng-d01.db.aol.com:27017,ec2-184-73-54-43.compute-1.amazonaws.com:27017, terminating

      Looks like map/reduce isn't handling certain socket errors correctly.

            Assignee:
            antoine Antoine Girbal
            Reporter:
            antoine Antoine Girbal
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: