Running yb-ctl status does not give the node information

General
1

Hi, I was trying to manually deploy yugabyte db in my docker container with three nodes(three containers) and a replication factor of three. Things seem to work as expected but when I tried to run yb-ctl status with the directory the data is stored as input, it shows this:

image
image725×171 5.02 KB

while i tried to create a table in one of the containers and access it on another one, it works fine. And the nodetool also gives me the expected number of nodes.

Is this expected or did I do something wrong?

Thank you!

3

I think you should use yb-docker-ctl - command line tool for administering local Docker-based clusters | YugabyteDB Docs which manages a cluster with local containers.

Does that work for you ?

4

Thanks for your reply. Let me show the steps that I have followed:

  1. Create my own docker images and download yugabyte inside my image.(I have to control the users and different settings inside my containers.)
  2. run 3 containers with my docker image in a VM and provide the master IP and location where data is to be stored with RF = 3. I run yb-master and yb-tserver scripts after my docker container is up with the required arguments.
  3. Check the logs for master and tserver and everything is working fine.
  4. Connect to Yuga Cassandra using cqlsh with my IP and port.
  5. Create a keyspace and table.
  6. Connect to a different yuga container that I had run earlier, connect to cassandra and see the keyspace and table created.
  7. Do the yb-ctl status as shown in the image above, and I don’t see my cluster, which according to my understanding should have 3 nodes and RF = 3.

Commands that I run to start my yb-master and yb-tserver. Let me know if you would like to see the logs as well.

./yb-master
–master_addresses=172.25.2.50:7100,172.25.2.51:7100,172.25.2.52:7100
–rpc_bind_addresses={current IP of my container}
–fs_data_dirs=/opt/yugabyteDB/data
–replication_factor=3

./yb-tserver
–tserver_master_addrs=172.25.2.50:7100,172.25.2.51:7100,172.25.2.52:7100
–rpc_bind_addresses={current IP of my container}
–cql_proxy_bind_address={current IP of my container}:9042
–fs_data_dirs=/opt/yugabyteDB/data

5

Hi @AndrewLiuRM

The yb-ctl status is only meant to be used for local clusters that are created using yb-ctl itself.

For your setup, try:

http://172.25.2.50:7000/

or

http://172.25.2.50:7000/tablet-servers

to view the nodes in the cluster.

1 Like
6

Got it! I tried both and it seems like everything is working well! Thank you!

1 Like
7

Awesome. Glad to hear!