Getlasterror call return wrong result when the previous write op has chunk splitt

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.7
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The reason from the source code:
      1. update/insert invoke chunk splitting;
      2. splitIfShould call ShardConnection::sync();
      3. sync function send getlasterror command to the shard;
      4. then the shard exec splitting;
      5. when our api call getlasterror later, we will get wrong result

            Assignee:
            Unassigned
            Reporter:
            Jack Chan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: