​

Field Details

• ​

  REBALANCE_SHARDED_DATA

  public static final String REBALANCE_SHARDED_DATA

  If TRUE, sharded data will be rebalanced approximately equally across the cluster. Note that for clusters with large amounts of sharded data, this data transfer could be time consuming and result in delayed query responses. Supported values:

  • TRUE
  • FALSE

  The default value is TRUE.

  See Also:

  • Constant Field Values

• ​

  TRUE

  public static final String TRUE

  See Also:

  • Constant Field Values

• ​

  FALSE

  public static final String FALSE

  See Also:

  • Constant Field Values

• ​

  REBALANCE_UNSHARDED_DATA

  public static final String REBALANCE_UNSHARDED_DATA

  If TRUE, unsharded data (a.k.a. randomly-sharded) will be rebalanced approximately equally across the cluster. Note that for clusters with large amounts of unsharded data, this data transfer could be time consuming and result in delayed query responses. Supported values:

  • TRUE
  • FALSE

  The default value is TRUE.

  See Also:

  • Constant Field Values

• ​

  TABLE_INCLUDES

  public static final String TABLE_INCLUDES

  Comma-separated list of unsharded table names to rebalance. Not applicable to sharded tables because they are always rebalanced. Cannot be used simultaneously with TABLE_EXCLUDES. This parameter is ignored if REBALANCE_UNSHARDED_DATA is FALSE.

  See Also:

  • Constant Field Values

• ​

  TABLE_EXCLUDES

  public static final String TABLE_EXCLUDES

  Comma-separated list of unsharded table names to not rebalance. Not applicable to sharded tables because they are always rebalanced. Cannot be used simultaneously with TABLE_INCLUDES. This parameter is ignored if REBALANCE_UNSHARDED_DATA is FALSE.

  See Also:

  • Constant Field Values

• ​

  AGGRESSIVENESS

  public static final String AGGRESSIVENESS

  Influences how much data is moved at a time during rebalance. A higher AGGRESSIVENESS will complete the rebalance faster. A lower AGGRESSIVENESS will take longer but allow for better interleaving between the rebalance and other queries. Valid values are constants from 1 (lowest) to 10 (highest). The default value is ‘10’.

  See Also:

  • Constant Field Values

• ​

  COMPACT_AFTER_REBALANCE

  public static final String COMPACT_AFTER_REBALANCE

  Perform compaction of deleted records once the rebalance completes to reclaim memory and disk space. Default is TRUE, unless REPAIR_INCORRECTLY_SHARDED_DATA is set to TRUE. Supported values:

  • TRUE
  • FALSE

  The default value is TRUE.

  See Also:

  • Constant Field Values

• ​

  COMPACT_ONLY

  public static final String COMPACT_ONLY

  If set to TRUE, ignore rebalance options and attempt to perform compaction of deleted records to reclaim memory and disk space without rebalancing first. Supported values:

  • TRUE
  • FALSE

  The default value is FALSE.

  See Also:

  • Constant Field Values

• ​

  REPAIR_INCORRECTLY_SHARDED_DATA

  public static final String REPAIR_INCORRECTLY_SHARDED_DATA

  Scans for any data sharded incorrectly and re-routes the data to the correct location. Only necessary if GPUdb.adminVerifyDb reports an error in sharding alignment. This can be done as part of a typical rebalance after expanding the cluster or in a standalone fashion when it is believed that data is sharded incorrectly somewhere in the cluster. Compaction will not be performed by default when this is enabled. If this option is set to TRUE, the time necessary to rebalance and the memory used by the rebalance may increase. Supported values:

  • TRUE
  • FALSE

  The default value is FALSE.

  See Also:

  • Constant Field Values