无法在具有首选区域的多区域部署中在 YugbyteDB 中创建表

Question

[用户在YugabyteDB社区Slack上发布的问题]

我在3个不同的区域部署了一个3主+ 3服务器集群。我正在尝试设置首选区域。

即使每个主机都在不同的区域，我也必须使用https://docs.yugabyte.com/latest/admin/yb-admin/#modify-placement-info以便在配置中显示。然后我使用:https://docs.yugabyte.com/latest/admin/yb-admin/#set-preferred-zones来设置首选区域。

但是平板电脑并没有重新平衡领导者。还有什么事要做吗?

样本yb-tserver.conf

/home/yugabyte/bin/yb-tserver 
--fs_data_dirs=/mnt/disk0 
--tserver_master_addrs={yb-master-0.yb-masters.yugabyte1.svc.cluster.local:7100,nyzks901i:29600},ldzks449i:29605,sgzks449i:29601 
--placement_region=nyz-core-prod 
--use_private_ip=never 
--server_broadcast_addresses=nyzks902i:29500 
--metric_node_name=yb-tserver-0 
--memory_limit_hard_bytes=3649044480 
--stderrthreshold=0 --num_cpus=0 
--undefok=num_cpus,enable_ysql 
--rpc_bind_addresses=yb-tserver-0.yb-tservers.yugabyte1.svc.cluster.local 
--webserver_interface=0.0.0.0 
--enable_ysql=true 
--pgsql_proxy_bind_address=0.0.0.0:5433 
--cql_proxy_bind_address=yb-tserver-0.yb-tservers.yugabyte1.svc.cluster.local

样本yb-master.conf

/home/yugabyte/bin/yb-tserver 
--fs_data_dirs=/mnt/disk0 
--tserver_master_addrs={yb-master-0.yb-masters.yugabyte1.svc.cluster.local:7100,nyzks901i:29600},ldzks449i:29605,sgzks449i:29601 
--placement_region=nyz-core-prod 
--use_private_ip=never 
--server_broadcast_addresses=nyzks902i:29500 
--metric_node_name=yb-tserver-0 
--memory_limit_hard_bytes=3649044480 
--stderrthreshold=0 
--num_cpus=0 
--undefok=num_cpus,enable_ysql 
--rpc_bind_addresses=yb-tserver-0.yb-tservers.yugabyte1.svc.cluster.local 
--webserver_interface=0.0.0.0 
--enable_ysql=true 
--pgsql_proxy_bind_address=0.0.0.0:5433 
--cql_proxy_bind_address=yb-tserver-0.yb-tservers.yugabyte1.svc.cluster.local

即使创建一个新表也会导致错误:

cur.execute(
...   """
...   CREATE TABLE employee (id int PRIMARY KEY,
...                          name varchar,
...                          age int,
...                          language varchar)
...   """)
Traceback (most recent call last):
File "<stdin>", line 7, in <module>
psycopg2.errors.InternalError_: Invalid argument: Invalid table definition: Timed out waiting for Table Creation

和下面的yb-tserver日志在上面的错误:

W0806 15:00:55.004124    63 catalog_manager.cc:7475] Aborting the current task due to error: Invalid argument (yb/master/catalog_manager.cc:7623): An error occurred while selecting replicas for tablet 0a503b0b9196425c956a8b9939b2c370: Invalid argument (yb/master/catalog_manager.cc:7623): Not enough tablet servers in the requested placements. Need at least 3, have 1: Not enough tablet servers in the requested placements. Need at least 3, have 1
E0806 15:00:55.004171    63 catalog_manager_bg_tasks.cc:142] Error processing pending assignments, aborting the current task: Invalid argument (yb/master/catalog_manager.cc:7623): An error occurred while selecting replicas for tablet 0a503b0b9196425c956a8b9939b2c370: Invalid argument (yb/master/catalog_manager.cc:7623): Not enough tablet servers in the requested placements. Need at least 3, have 1: Not enough tablet servers in the requested placements. Need at least 3, have 1
I0806 15:00:55.139647  2352 ysql_transaction_ddl.cc:46] Verifying Transaction { transaction_id: bb93b749-6b57-41b6-8f50-7461a07dc254 isolation: SNAPSHOT_ISOLATION status_tablet: 4069e18783a747bea31895b3ab6c69f6 priority: 1756854571847405073 start_time: { physical: 1628261964493502 } }
I0806 15:00:55.295994    53 ysql_transaction_ddl.cc:77] TransactionReceived: OK : status: PENDING
status_hybrid_time: 6669361378174894079
propagated_hybrid_time: 6669361378174910464
I0806 15:00:55.296051    53 ysql_transaction_ddl.cc:97] Got Response for { transaction_id: bb93b749-6b57-41b6-8f50-7461a07dc254 isolation: SNAPSHOT_ISOLATION status_tablet: 4069e18783a747bea31895b3ab6c69f6 priority: 1756854571847405073 start_time: { physical: 1628261964493502 } }: status: PENDING
status_hybrid_time: 6669361378174894079
propagated_hybrid_time: 6669361378174910464
W0806 15:00:55.310122    66 master_service_base-internal.h:39] Unknown master error in status: Invalid argument (yb/master/catalog_manager.cc:7623): An error occurred while selecting replicas for tablet 0a503b0b9196425c956a8b9939b2c370: Invalid argument (yb/master/catalog_manager.cc:7623): Not enough tablet servers in the requested placements. Need at least 3, have 1: Not enough tablet servers in the requested placements. Need at least 3, have 1
I0806 15:00:55.496171  2352 ysql_transaction_ddl.cc:46] Verifying Transaction { transaction_id: bb93b749-6b57-41b6-8f50-7461a07dc254 isolation: SNAPSHOT_ISOLATION status_tablet: 4069e18783a747bea31895b3ab6c69f6 priority: 1756854571847405073 start_time: { physical: 1628261964493502 } }
I0806 15:00:55.652542    67 ysql_transaction_ddl.cc:77] TransactionReceived: OK : status: PENDING

Answer 1

除了Dorian的回答:请显示并验证完整的放置信息。你可以这样做:

• 主位置信息可以使用curl http://MASTER-ADDRESS:7000/api/v1/masters | jq.
• 服务器位置信息可以在http://MASTER-ADDRESS:7000/tablet-servers上找到(通过浏览器)。
• 使用curl http://MASTER-ADDRESS:7000/cluster-config | jq的首选区域概述

这样，应该很容易看到和验证是否一切都设置好了。

Answer 2

您还需要您的yb-tserver进程的--placement_cloud=cloud和--placement_zone=rack1参数(以匹配您传递给modify_placement_info步骤的参数)。不仅仅是--placement_regiongflag。

否则，create table步骤不会找到匹配的TServers来满足表的期望位置。