alter move

Suspend, resume, or cancel scheduled chunk move operations on a sharded database.

Syntax

ALTER MOVE {-RESUME|-SUSPEND|-CANCEL}
         [-CHUNK {chunk_id_list}]
         [-SHARD shd_lst]
         [-verbose] 
         

Options

Table 2-16 GDSCTL ALTER MOVE Options

Option	Description
-cancel	Removes chunks from the pending chunk moves list for the specified scope.
-chunk chunk_id_list	List comma separated numeric chunk identifiers or use ALL for all chunks in the sharded database.
-resume	Resumes (reschedules) chunk moves which are in the "move failed" state for the specified scope.
-shard shd_lst	A comma separated list of shards.
-suspend	Suspends pending chunk moves for the specified scope.
-verbose	Enables verbose output mode.

Usage Notes

Suspending chunk moves: Use ALTER MOVE -SUSPEND to postpone a pending chunk move.

Resuming chunk moves: Use ALTER MOVE -RESUME to place specified chunk moves that are suspended or stalled (in the "move failed" state) into the "scheduled" state, effectively rescheduling them.

Canceling chunk moves: Use ALTER MOVE -CANCEL to cancel pending chunk moves. Once a chunk move operation is canceled it cannot be resumed or suspended.

Use the -chunk and -shard options to filter the scheduled chunk move operations. Use the -chunk option to target specific chunk IDs, and use the -shard option to target all chunk moves scheduled to occur to and from the specified database.

You can use the CONFIG CHUNKS command to get a list of pending chunk moves.

Chunk moves that are already in process cannot be suspended or canceled. If any chunk in scope for the ALTER MOVE operation is already in any state other than "scheduled" a warning is returned indicating that the move operation for that chunk was not altered.

Examples

Suspend all pending chunk moves:

ALTER MOVE -SUSPEND

Resume (reschedule) move operations for chunks 3 and 4:

ALTER MOVE -RESUME -CHUNK 3,4

Cancel all pending chunk moves to and from shard SH_1:

ALTER MOVE -CANCEL -SHARD SH_1