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

stale mongod view of shards causes m/r error

XMLWordPrintableJSON

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

      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.

        1. mr_stale_shards.js
          2 kB

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: