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

stale mongod view of shards causes m/r error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.6, 2.1.2
    • Fix Version/s: None
    • Component/s: MapReduce, Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      If a shard is removed during the M/R process, due to SERVER-5625, it is possible the shardedFinish will try to contact the stale shard and fail.

      2.1.2 improves the error message but does not fully solve. There isn't a way currently to manually refresh the shard view aside from triggering a migration (only in 2.1.2).

      Better messaging should be put around socket exceptions due to SERVER-5625, as the nested exception is pretty confusing to track.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: