Question: I don't add vttablet into vitess cluster on a new node.

[czxin788]

Question

I follow the 101_initial_cluster.sh script by https://vitess.io/docs/19.0/get-started/local/, and I deploy a local single vitess cluster:

node: 10.221.252.139
mysql> show vitess_tablets;
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
| Cell  | Keyspace     | Shard | TabletType | State       | Alias            | Hostname                 | PrimaryTermStartTime |
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
| zone1 | commerce     | 0     | PRIMARY    | SERVING     | zone1-0000000101 | database-vitess01.dev.zs | 2024-05-14T05:13:41Z |
| zone1 | commerce     | 0     | REPLICA    | SERVING     | zone1-0000000100 | database-vitess01.dev.zs |                      |
| zone1 | commerce     | 0     | RDONLY     | SERVING     | zone1-0000000102 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | -40   | PRIMARY    | SERVING     | zone1-0000000200 | database-vitess01.dev.zs | 2024-05-14T05:23:37Z |
| zone1 | db12_qlw_ylw | -40   | REPLICA    | SERVING     | zone1-0000000201 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | -40   | RDONLY     | SERVING     | zone1-0000000202 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 40-80 | PRIMARY    | SERVING     | zone1-0000000301 | database-vitess01.dev.zs | 2024-05-14T09:18:13Z |
| zone1 | db12_qlw_ylw | 40-80 | REPLICA    | SERVING     | zone1-0000000300 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 40-80 | RDONLY     | SERVING     | zone1-0000000302 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 80-c0 | PRIMARY    | NOT_SERVING | zone1-0000000400 | database-vitess01.dev.zs | 2024-05-14T10:12:35Z |
| zone1 | db12_qlw_ylw | 80-c0 | REPLICA    | NOT_SERVING | zone1-0000000401 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 80-c0 | RDONLY     | NOT_SERVING | zone1-0000000402 | database-vitess01.dev.zs |                      |
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
12 rows in set (0.00 sec)

And I bring up mysqld and vttablet on another node 10.221.252.140 for join to the vitess cluster:

mysqlctl --config-file-not-found-handling=ignore --log_dir /home/vitess/vtdataroot//tmp --tablet_uid 500 --mysql_port 17500 init


vttablet --config-file-not-found-handling=ignore --topo_implementation etcd2 --topo_global_server_address 10.221.252.139:2379 --topo_global_root /vitess/global --log_dir /home/vitess/vtdataroot/tmp --log_queries_to_file /home/vitess/vtdataroot//tmp/vttablet_0000000500_querylog.txt --tablet-path zone1-0000000500 --tablet_hostname '' --init_keyspace nxin_qlw_ylw --init_shard c0-d0 --init_tablet_type replica --health_check_interval 5s --backup_storage_implementation file --file_backup_storage_root /home/vitess/vtdataroot/backups --restore_from_backup --port 15500 --grpc_port 16500 --service_map grpc-queryservice,grpc-tabletmanager,grpc-updatestream --pid_file /home/vitess/vtdataroot/vt_0000000500/vttablet.pid --heartbeat_on_demand_duration=5s &

But I t can not add the new tablet zone1-000000050 on the new node 10.221.252.140 into vitess cluster, and show vitess_tablets always display old results:

mysql> show vitess_tablets;
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
| Cell  | Keyspace     | Shard | TabletType | State       | Alias            | Hostname                 | PrimaryTermStartTime |
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
| zone1 | commerce     | 0     | PRIMARY    | SERVING     | zone1-0000000101 | database-vitess01.dev.zs | 2024-05-14T05:13:41Z |
| zone1 | commerce     | 0     | REPLICA    | SERVING     | zone1-0000000100 | database-vitess01.dev.zs |                      |
| zone1 | commerce     | 0     | RDONLY     | SERVING     | zone1-0000000102 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | -40   | PRIMARY    | SERVING     | zone1-0000000200 | database-vitess01.dev.zs | 2024-05-14T05:23:37Z |
| zone1 | db12_qlw_ylw | -40   | REPLICA    | SERVING     | zone1-0000000201 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | -40   | RDONLY     | SERVING     | zone1-0000000202 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 40-80 | PRIMARY    | SERVING     | zone1-0000000301 | database-vitess01.dev.zs | 2024-05-14T09:18:13Z |
| zone1 | db12_qlw_ylw | 40-80 | REPLICA    | SERVING     | zone1-0000000300 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 40-80 | RDONLY     | SERVING     | zone1-0000000302 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 80-c0 | PRIMARY    | NOT_SERVING | zone1-0000000400 | database-vitess01.dev.zs | 2024-05-14T10:12:35Z |
| zone1 | db12_qlw_ylw | 80-c0 | REPLICA    | NOT_SERVING | zone1-0000000401 | database-vitess01.dev.zs |                      |
| zone1 | db12_qlw_ylw | 80-c0 | RDONLY     | NOT_SERVING | zone1-0000000402 | database-vitess01.dev.zs |                      |
+-------+--------------+-------+------------+-------------+------------------+--------------------------+----------------------+
12 rows in set (0.00 sec)

I don't know why, and what can I do.

My English is a bit weak, I don't know if my question description is clear

[mattlord]

This is not really a question, but a request for help/support. Please raise this in the #beginners channel in the Vitess Slack so that the entire vitess community can help (only a few maintainers might see this and it's not used as a support channel in that way in the project).

I'm going to close this. You can ping me there on Slack if you want to when you pose the problem in that channel. You'll need to start by looking at the vtgate and vttablet logs to see what the underlying cause(s) are. It could be a myriad of things (many environment dependent and nobody knows the full environment or has access to the logs but you).