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

getLastError "n" is 0 if previous writes goes through writebackListener

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Duplicate
    • Affects Version/s: 2.0.1
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
    • Operating System:
      ALL

      Description

      If a write hits the wrong shard, immediately after a migrate, and has to go through the writebackListener then the getLastError call returns n:0.

      We should indicate a special state (writeback:true, or n:-1, or something) if we can't correctly report the "n" value.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              scotthernandez Scott Hernandez
              Reporter:
              scotthernandez Scott Hernandez
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: