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

XMLWordPrintableJSON

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

      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:
              Scott Hernandez (Inactive)
              Reporter:
              Scott Hernandez (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: