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

[Resharding] Reject writes in opObserver when disallowWritesForResharding is true

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2021-01-25, Sharding 2021-02-22, Sharding 2021-03-08
    • 133
    • 2

    Description

      This is a stop-gap solution and doesn't have to be pretty. Just for now, reject writes when:

      1. The collection has reshardingFields, and
      2. The collection is in the states:
        1. kMirroring, or
        2. kRenaming and the UUID is the original collection.

      The above conditions are satisfied with the call to writesShouldRunInDistributedTransaction, which is the "blocking" state that's still named as the "distributed transaction" state.

      Suggestion: for now, create a named error code "WriteRejectedForResharding" that's easy to verify in a test. In Milestone 3, a more robust solution will be designed to possibly queue writes.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-53631 [Resharding] Verify UUIDs are correct in writesShouldRunInDistributedTransaction

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-53923 Enforce reshardingCriticalSectionTimeout parameter

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-53653 [Resharding] Take the critical section when renaming on recipient shards

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-54672 Enable test of writes succeeding after reshardCollection command completes

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-53911 Increment countWritesDuringCriticalSection

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-55852 Shards first acquire LockManager locks before reacting to abortReshardCollection

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-52742 Ensure both donorFields and recipientFields exists on the original collection entry after a resharding operation commits

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-57665 Remove the unused disallowWritesForResharding() method

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              alex.taskov@mongodb.com Alexander Taskov (Inactive)
              blake.oler@mongodb.com Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: