Skip to content

Conversation

@ShooterIT
Copy link
Member

Currently, we use cluster command to set cluster topology, as we know, we must allow users use cluster command to get nodes and slots, and we only can rename command name instead of subcommand, that is to say, users have a chance to change cluster topology, it is dangerous.

Now, we use clusterx command to set cluster topology, you can rename it if you don't want to expose this command to users.

@ShooterIT ShooterIT requested review from git-hulk and karelrooted July 9, 2021 08:25
@ShooterIT ShooterIT mentioned this pull request Jul 14, 2021
@ShooterIT ShooterIT changed the title Use clusterx command to set cluster topology Use CLUSTERX command to set cluster topology Jul 14, 2021
@ShooterIT ShooterIT merged commit ad382f7 into apache:unstable Jul 14, 2021
@ShooterIT ShooterIT deleted the clusterx branch July 14, 2021 13:00
ShooterIT added a commit to ShooterIT/kvrocks that referenced this pull request Jul 15, 2021
Currently, we use cluster command to set cluster topology, as we know,
we must allow users use cluster command to get nodes and slots, and we
only can rename command name instead of subcommand, that is to say, users
have a chance to change cluster topology, it is dangerous.

Now, we use CLUSTERX command to set cluster topology, you can rename it
if you don't want to expose this command to users.
@ShooterIT ShooterIT mentioned this pull request Jul 15, 2021
ShooterIT added a commit that referenced this pull request Jul 19, 2021
Currently, we use cluster command to set cluster topology, as we know,
we must allow users use cluster command to get nodes and slots, and we
only can rename command name instead of subcommand, that is to say, users
have a chance to change cluster topology, it is dangerous.

Now, we use CLUSTERX command to set cluster topology, you can rename it
if you don't want to expose this command to users.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants