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

Need to add instructions to run setup_redis before using redis-cli #1547

Open
ramkumarvs opened this issue Jun 14, 2019 · 6 comments
Open

Need to add instructions to run setup_redis before using redis-cli #1547

ramkumarvs opened this issue Jun 14, 2019 · 6 comments
Labels
help wanted We welcome your contributions for this issue! kind/bug This issue is a bug kind/enhancement This is an enhancement of an existing feature

Comments

@ramkumarvs
Copy link
Contributor

Right now when we run yb-ctl create we print the different connect strings, but redis would not work unless we run yb-ctl setup_redis or we need to bundle that into the yb-ctl create call.

If I tried to run redis without running setup redis we would see this error.

➜  yugabyte-1.2.10.0 ./bin/redis-cli -h 127.0.0.1
127.0.0.1:6379> set foo bar
(error) ERR set: Could not open YBTable
@ramkumarvs ramkumarvs added kind/bug This issue is a bug kind/enhancement This is an enhancement of an existing feature labels Jun 14, 2019
@ramkumarvs ramkumarvs added this to To do in User Experience via automation Jun 14, 2019
@rkarthik007 rkarthik007 added the help wanted We welcome your contributions for this issue! label Jun 17, 2019
@zeinali0
Copy link

zeinali0 commented Mar 2, 2020

I face with this error when i run yb-ctl setup_redis
ValueError: Cannot form yb-admin command without knowing master addresses

@ndeodhar
Copy link
Contributor

ndeodhar commented Mar 2, 2020

@zeinali0 This is likely because you don't already have a cluster set up. You'll need to first run
./bin/yb-ctl create : This will create the yugabyteDB cluster and then run
./bin/yb-ctl setup_redis : This will setup redis in the cluster, enabling you to use the redis cli.

@zeinali0
Copy link

zeinali0 commented Mar 2, 2020

i start masters and tservers manually according to this.
Should i run ./bin/yb-ctl create too?

Update
While every thing is working on YCQL i found --master_addresses= not set in my gflags of tservers.

@schoudhury
Copy link
Contributor

Manual deployment is an alternative to yb-ctl so you should not use yb-ctl here. You should follow this step in order setup the YEDIS API:
https://docs.yugabyte.com/latest/deploy/manual-deployment/verify-deployment/#optional-setup-yedis-api

@zeinali0
Copy link

zeinali0 commented Mar 3, 2020

Manual deployment is an alternative to yb-ctl so you should not use yb-ctl here. You should follow this step in order setup the YEDIS API:
https://docs.yugabyte.com/latest/deploy/manual-deployment/verify-deployment/#optional-setup-yedis-api

I couldn't find how create 3 cluster on 3 different node wit ./bin/yb-ctl create? I didn't see any where mentioned --master_addresses for this command.
Is it possible? or it's just for local cluster.

@ndeodhar
Copy link
Contributor

ndeodhar commented Mar 3, 2020

@zeinali0 yb-ctl is just for local clusters and uses 127.0.0.1 master address. You cannot setup a true multi-node cluster using yb-ctl.
If you want to use local cluster to try out yugabyteDB and redis, you'll need to do:

./bin/yb-ctl create
./bin/yb-ctl setup_redis

However, if you want a true multi-node cluster, then you can follow the steps in manual deployment:
https://docs.yugabyte.com/latest/deploy/manual-deployment/
Once your cluster is created, you can setup redis API using:
./bin/yb-admin --master_addresses 172.151.17.130:7100,172.151.17.220:7100,172.151.17.140:7100 setup_redis_table
Note: replace the master addresses above with your IPs.

Let me know if you have any further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted We welcome your contributions for this issue! kind/bug This issue is a bug kind/enhancement This is an enhancement of an existing feature
Projects
Development

No branches or pull requests

5 participants