public static final class AdminRebalanceRequest.Options extends Object
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:
The default value is TRUE
.
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:
The default value is TRUE
.
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
.
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
.
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'.
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:
The default value is TRUE
.
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:
The default value is FALSE
.
REPAIR_INCORRECTLY_SHARDED_DATA
: Scans for any data sharded incorrectly
and re-routes the data to the correct location. Only necessary if GPUdb.adminVerifyDb(AdminVerifyDbRequest)
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:
The default value is FALSE
.
Map
.
A set of string constants for the parameter options
.Modifier and Type | Field and Description |
---|---|
static String |
AGGRESSIVENESS
Influences how much data is moved at a time during rebalance.
|
static String |
COMPACT_AFTER_REBALANCE
Perform compaction of deleted records once the rebalance completes
to reclaim memory and disk space.
|
static 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. |
static String |
FALSE |
static String |
REBALANCE_SHARDED_DATA
|
static String |
REPAIR_INCORRECTLY_SHARDED_DATA
Scans for any data sharded incorrectly and re-routes the data to the
correct location.
|
static String |
TABLE_EXCLUDES
Comma-separated list of unsharded table names to not rebalance.
|
static String |
TABLE_INCLUDES
Comma-separated list of unsharded table names to rebalance.
|
static String |
TRUE |
public static final String REBALANCE_SHARDED_DATA
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:
The default value is TRUE
.public static final String TRUE
public static final String FALSE
public static final String REBALANCE_UNSHARDED_DATA
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:
The default value is TRUE
.public static final String TABLE_INCLUDES
table_excludes
. This
parameter is ignored if rebalance_unsharded_data
is false
.public static final String TABLE_EXCLUDES
table_includes
. This
parameter is ignored if rebalance_unsharded_data
is false
.public static final String AGGRESSIVENESS
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'.public static final String COMPACT_AFTER_REBALANCE
true
, unless
repair_incorrectly_sharded_data
is set to true
.
Supported values:
The default value is TRUE
.public static final String COMPACT_ONLY
true
, ignore rebalance options and attempt to
perform compaction of deleted records to reclaim memory and disk
space without rebalancing first.
Supported values:
The default value is FALSE
.public static final String REPAIR_INCORRECTLY_SHARDED_DATA
GPUdb.adminVerifyDb(AdminVerifyDbRequest)
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:
The default value is FALSE
.Copyright © 2024. All rights reserved.