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

Implement serverStatus section with active migrations

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.12
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 18 (08/05/16), Sharding 2016-08-29

      Description

      Implement an optional serverStatus section, available both on the config server and on the shards, which returns information about all the active chunk migrations. This section will be used by support and possibly by the balancer when it resumes from primary stepdown.

      On the shards, this serverStatus section should look like this (and should be placed under the optional sharding section):

      sharding: {
      	migrations: [
      		{ source: ShardId,
                        sourceHost: Host:Port,
                        destination: ShardId,
                        destinationHost: Host:Port,
                        chunk: { min: <MinKey>, max: <MaxKey> },
                        phase: String, one of <INIT, CATCHUP, CRITICAL SECTION>,
      		},
      		...
      	]
      }
      

      On the config server, the section should be the union of all migrations across all shards.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: