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

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

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.0.1
    • Component/s: Sharding
    • ALL

      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.

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

              Created:
              Updated:
              Resolved: