KunlunBase is a distributed relational database management system(RDBMS) with complete NewSQL capabilities and robust transaction ACID guarantees and is compatible with standard SQL. Applications which used PostgreSQL or MySQL can work with KunlunBase as-is without any code change or rebuild because KunlunBase supports both PostgreSQL and MySQL connection protocols and DML SQL grammars. MySQL DBAs can quickly work on a KunlunBase cluster because we use MySQL as storage nodes of KunlunBase. KunlunBase can elastically scale out as needed, and guarantees transaction ACID under error conditions, and KunlunBase fully passes TPC-C, TPC-H and TPC-DS test suites, so it not only support OLTP workloads but also OLAP workloads. Application developers can use KunlunBase to build IT systems that handles terabytes of data, without any effort on their part to implement data sharding, distributed transaction processing, distributed query processing, crash safety, high availability, strong consistency, horizontal scalability. All these powerful features are provided by KunlunBase. KunlunBase supports powerful and user friendly cluster management, monitor and provision features, can be readily used as DBaaS.
Too many connection established from CN “topo service” to meta server。
The stack of “topo service” is:
#0 0x00007fe82053ba08 in poll () from /lib64/libc.so.6
#1 0x00007fe820f9e7c9 in pvio_socket_wait_io_or_timeout () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#2 0x00007fe820f9eb1a in pvio_socket_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#3 0x00007fe820fabb7f in ma_pvio_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#4 0x00007fe820fabd63 in ma_pvio_cache_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#5 0x00007fe820fa18a6 in ma_real_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#6 0x00007fe820fa26ed in ma_net_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#7 0x00007fe820fa7621 in ma_net_safe_read () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#8 0x00007fe820f9e19f in run_plugin_auth () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#9 0x00007fe820fa8d39 in mthd_my_real_connect () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#10 0x00007fe820fa55d2 in mysql_real_connect () from /home/kunlun/compare/base/kunlun-server-0.9.1/lib/libmariadb.so.3
#11 0x00000000008a965b in connect_mysql (mysql=0x1045120 <cnconn>, host=0x7fe81df142c8 "192.168.0.140", port=6002, user=0x1044ad8 <cmnodes+88> "pgx",
password=0x7fe81df142f0 "pgx_pwd", is_bg=true, check_master=-1) at cluster_meta.c:287
#12 0x00000000008aaa8a in check_metashard_master (cnconn=0x1045120 <cnconn>, ci=0x1044ad8 <cmnodes+88>, cis=0x1044a80 <cmnodes>, num_ci=3) at cluster_meta.c:785
#13 0x00000000008ab351 in FindCurrentMetaShardMasterNodeId (pmaster_nodeid=0x7ffc06085824, old_master_nodeid=0x7ffc06085820) at cluster_meta.c:980
#14 0x00000000008ab88e in UpdateCurrentMetaShardMasterNodeId () at cluster_meta.c:1075
#15 0x00000000005bab8f in ProcessShardingTopoReqs () at pg_sharding.c:1245
#16 0x00000000005bbef6 in TopoServiceMain () at pg_sharding.c:1793
#17 0x0000000000579291 in AuxiliaryPr
Issue migrated from trac ticket # 524
component: computing nodes | priority: major
2022-03-28 17:26:11: smith created the issue