gpmovemirrors

Moves mirror segment instances to new locations.

Synopsis

  1. gpmovemirrors -i <move_config_file> [-d <master_data_directory>] 
  2.           [-l <logfile_directory>] [-b <segment_batch_size>]
  3.           [-B <batch_size>] [-v] [--hba-hostnames <boolean>] 
  5. gpmovemirrors -? 
  7. gpmovemirrors --version

Description

The gpmovemirrors utility moves mirror segment instances to new locations. You may want to move mirrors to new locations to optimize distribution or data storage.

By default, the utility will prompt you for the file system location(s) where it will move the mirror segment data directories.

You must make sure that the user who runs gpmovemirrors (the gpadmin user) has permissions to write to the data directory locations specified. You may want to create these directories on the segment hosts and chown them to the appropriate user before running gpmovemirrors.

Options

-b segment_batch_size

The maximum number of segments per host to operate on in parallel. Valid values are 1 to 128. If not specified, the utility will start recovering up to 64 segments in parallel on each host.

-B batch_size

The number of hosts to work on in parallel. If not specified, the utility will start working on up to 16 hosts in parallel. Valid values are 1 to 64.

-d master_data_directory

The master data directory. If not specified, the value set for $MASTER_DATA_DIRECTORY will be used.

–hba-hostnames boolean

Optional. Controls whether this utility uses IP addresses or host names in the pg_hba.conf file when updating this file with addresses that can connect to Greenplum Database. When set to 0 – the default value – this utility uses IP addresses when updating this file. When set to 1, this utility uses host names when updating this file. For consistency, use the same value that was specified for HBA_HOSTNAMES when the Greenplum Database system was initialized. For information about how Greenplum Database resolves host names in the pg_hba.conf file, see Configuring Client Authentication.

-i move_config_file

A configuration file containing information about which mirror segments to move, and where to move them.

You must have one mirror segment listed for each primary segment in the system. Each line inside the configuration file has the following format (as per attributes in the gp_segment_configuration catalog table):

  1. <old_address>|<port>|<data_dir> <new_address>|<port>|<data_dir>

Where <old_address> and <new_address> are the host names or IP addresses of the segment hosts, <port> is the communication port, and <data_dir> is the segment instance data directory.

-l logfile_directory

The directory to write the log file. Defaults to ~/gpAdminLogs.

-v (verbose)

Sets logging output to verbose.

–version (show utility version)

Displays the version of this utility.

-? (help)

Displays the online help.

Examples

Moves mirrors from an existing Greenplum Database system to a different set of hosts:

  1. $ gpmovemirrors -i move_config_file

Where the move_config_file looks something like this:

  1. sdw2|50000|/data2/mirror/gpseg0 sdw3|50000|/data/mirror/gpseg0
  2. sdw2|50001|/data2/mirror/gpseg1 sdw4|50001|/data/mirror/gpseg1
  3. sdw3|50002|/data2/mirror/gpseg2 sdw1|50002|/data/mirror/gpseg2