Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to disable rebalancer in sharding #9657

Closed
ImeevMA opened this issue Feb 7, 2024 · 0 comments · Fixed by #9661
Closed

Allow to disable rebalancer in sharding #9657

ImeevMA opened this issue Feb 7, 2024 · 0 comments · Fixed by #9661
Assignees
Labels
3.1 Target is 3.1 and all newer release/master branches config feature A new functionality

Comments

@ImeevMA
Copy link
Collaborator

ImeevMA commented Feb 7, 2024

The vshard module has the rebalancer_mode option. We need to add it to the config options.

@ImeevMA ImeevMA added the config label Feb 7, 2024
@ImeevMA ImeevMA self-assigned this Feb 7, 2024
ImeevMA added a commit to ImeevMA/tarantool that referenced this issue Feb 7, 2024
Closes tarantool#9657

@TarantoolBot document
Title: The `sharding.rebalancer_mode` option

The `sharding.rebalancer_mode` option can have one of three values:
`manual`, `auto` and `off`. Default value is `auto`.

If the option is set to `manual`, one of the replicasets must have the
`rebalancer` sharding role. The rebalancer will be in this replicaset.

If the option value is `auto` and there are no replicasets with the
sharding role `rebalancer`, the replicaset with rebalancer will
be selected automatically among all replicasets. If the value of the
parameter is `auto` and one of the replicasets has the sharding role
`rebalancer`, then the rebalancer will be in that replicaset.

If the option value is `off`, rebalancing will be disabled regardless of
whether a replicaset with the sharding role `rebalancer` exists or no
such replicaset exists.
@Totktonada Totktonada added 3.1 Target is 3.1 and all newer release/master branches feature A new functionality labels Feb 7, 2024
ImeevMA added a commit to ImeevMA/tarantool that referenced this issue Feb 8, 2024
Closes tarantool#9657

@TarantoolBot document
Title: The `sharding.rebalancer_mode` option

The `sharding.rebalancer_mode` option can have one of three values:
`manual`, `auto` and `off`. Default value is `auto`.

If the option is set to `manual`, one of the replicasets must have the
`rebalancer` sharding role. The rebalancer will be in this replicaset.

If the option value is `auto` and there are no replicasets with the
sharding role `rebalancer`, the replicaset with rebalancer will
be selected automatically among all replicasets. If the value of the
parameter is `auto` and one of the replicasets has the sharding role
`rebalancer`, then the rebalancer will be in that replicaset.

If the option value is `off`, rebalancing will be disabled regardless of
whether a replicaset with the sharding role `rebalancer` exists or no
such replicaset exists.
Totktonada pushed a commit that referenced this issue Feb 9, 2024
Closes #9657

@TarantoolBot document
Title: The `sharding.rebalancer_mode` option

The `sharding.rebalancer_mode` option can have one of three values:
`manual`, `auto` and `off`. Default value is `auto`.

If the option is set to `manual`, one of the replicasets must have the
`rebalancer` sharding role. The rebalancer will be in this replicaset.

If the option value is `auto` and there are no replicasets with the
sharding role `rebalancer`, the replicaset with rebalancer will
be selected automatically among all replicasets. If the value of the
parameter is `auto` and one of the replicasets has the sharding role
`rebalancer`, then the rebalancer will be in that replicaset.

If the option value is `off`, rebalancing will be disabled regardless of
whether a replicaset with the sharding role `rebalancer` exists or no
such replicaset exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.1 Target is 3.1 and all newer release/master branches config feature A new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants