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

Legacy MR shardedfinish can target a former primary

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: MapReduce, Replication
    • ALL
    • Query 2020-04-06
    • 39

      This causes the overall MR to fail with "not master and slaveOk=false" when trying to establish cursors on the shards, because the cursors are supposed to be against the primary but if there has been an election then the node the query is sent to might now be a secondary. It's not clear to me if the MR should just read from the secondary, or if this is just another failure mode of the legacy MR system (ie. it's simply not robust to any elections at any point during its runtime).

            Assignee:
            nicholas.zolnierz@mongodb.com Nicholas Zolnierz
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: