Implement the ability to block concurrent CRUD and DDL on MongoS

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-52755, SERVER-51755, SERVER-52754 and SERVER-52756 will all contribute to the ability to be able to block databases and collections for concurrent CRUD or DDL operations. The concurrent CRUD and DDL will fail by throwing a retryable BUSY-like exceptions.

      This ticket is to ensure these exceptions are not propagated to the driver invoking the concurrent CRUD or DDL, but are either blocked on the Shard or the Router, so that from the point of view of the client, they just appear as synchronisation, rather than error.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: