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

Reintroduce check for zoning/draining when serving manual chunk migrations in v6.0+ versions

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 7.0.1, 6.0.10, 7.1.0-rc3
    • None
    • Catalog and Routing
    • ALL
    • 2

    Description

      Up until v5.0 , when user was issuing a moveChunk command was being issued by a user, there was a check on the config server side ensuring that the chunk would not:

      • Span across multiple zones
      • Be moved to a draining shard

      With the introduction of the moveRange patch in v6.0, that check is not happening anymore.

      Purpose of this ticket is to evaluate if it's worth reintroducing such check for user-issued moveChunk/moveRange commands in v6.0+ versions. If yes, it should be reintroduced into this new balancer method.

      (Thanks tommaso.tocci@mongodb.com for spotting the change in behavior)

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: