search

zettadb / kunlun

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.
http://www.kunlunbase.com
Apache License 2.0
143 stars 20 forks source link

The length for ip field is not long enough for node #519

Open jd-zhang opened 3 years ago

jd-zhang commented 3 years ago

Issue migrated from trac ticket # 192

component: computing nodes | priority: major

2021-10-15 15:33:18: @jd-zhang created the issue

Currently, when using aurora as the data shard node, there is no private/public ipv4/ipv6 address for the node. There is just long dns-domain name, like following:

database-2-instance-1.ce15jbnan7m7.rds.cn-northwest-1.amazonaws.com.cn

kunlun-aurora-1-instance-1.ce15jbnan7m7.rds.cn-northwest-1.amazonaws.com.cn

They are longer than current limit in both pg_shard_node(using name as type, 64 bytes long), and kunlun_metadata_db.shard_nodes(varchar(64)).

Then shard node can not be added into the cluster.

We need to increase the limit, so that can support aurora as shard nodes, or similar cases, where only long-dns-name are provided for virtual instances.

jd-zhang commented 3 years ago

2021-10-19 18:58:47: @david-zhao

jd-zhang commented 3 years ago

2021-10-19 18:58:47: @david-zhao commented

fixed in revision 84fa41a4cef6229f83b0d14a8c4d05c1d646efe3

  1. Enlarge host address field(renamed from ip to hostaddr) in pg_shard_node and pg_cluster_meta_nodes tables, use text in place of NameData.
  2. Enlarge corresponding fields in corresponding metadata tables of metadata cluster.
  3. modify install scripts to go with new metadata format of computing nodes.
jd-zhang commented 3 years ago

2021-10-19 18:58:47: @david-zhao

jd-zhang commented 3 years ago

2021-10-19 18:58:47: @david-zhao changed owner from david to kunlun

jd-zhang commented 3 years ago

2021-10-19 18:58:47: @david-zhao changed status from assigned to accepted