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

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

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

      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 Unassigned
            Reporter:
            hustchensi chensi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: