Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11937

WriteConcern argument description is incorrect for the moveChunk command

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 3.4.0
    • Fix Version/s: 3.4.0
    • Component/s: Server
    • Labels:
      None

      Description

      Description

      Here we say this:

      writeConcern document Optional. A document that expresses the write concern that the _secondaryThrottle will use to wait for secondaries during the chunk migration. Any specified writeConcern implies _secondaryThrottle and will take precedent over a contradictory _secondaryThrottle setting.

      This implies that you can specify any combination of writeConcern and _secondaryThrottle arguments, and that should work. However, the server will only accept the command with writeConcern if _secondaryThrottle is not set to false:

      > db.runCommand({moveChunk:"test.docs", find: {x:60}, to: "shard02", _secondaryThrottle:false, writeConcern:{"w":3}})
      {
          "code" : 12,
          "ok" : 0,
          "errmsg" : "Cannot specify write concern when secondaryThrottle is not set"
      }
      

      Perhaps the following line needs to be removed:

      Any specified writeConcern implies _secondaryThrottle and will take precedent over a contradictory _secondaryThrottle setting.

      Scope of changes (files that need work and how much)

      Impact to other docs outside of this product

      MVP (work and date?)

      Resources (e.g. Scope Docs, Invision)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              dmitry.ryabtsev Dmitry Ryabtsev
              Participants:
              Last commenter:
              Anthony Sansone Anthony Sansone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 50 weeks, 6 days ago
                Date of 1st Reply: