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

Remove use of applyOps/doTxn from sharding chunk operations

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:

      Description

      Now that all chunk operations run in specialized config server commands, those commands can just do their multi-doc transaction writes directly in a single WUOW, there's no need to rely on applyOps/doTxn machinery. Doing this for 4.0 would allow us to remove support for atomic applyOps in 4.0, which is something the repl team is quite interested in.

        Attachments

          Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-33325 review use of "b" field in applyOps update operations in sharding_catalog_manager_chunk_operations.cpp

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-33182 Remove atomic applyOps

          • Major - P3 - Major loss of function.
          • Blocked
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-53502 Consider introducing fine grained chunk locks

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-58026 Omitted FTDC sections cause frequent schema changes that limit FTDC retention

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-50381 3 way deadlock between applyOps cmd, prepared transaction and secondary oplog fetcher initiated find command

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-36263 Bypassing operation validation in applyOps should require special privilege

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

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated: