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.
component: computing nodes | priority: major | resolution: finished
2021-09-27 19:10:05: zhaowei@zettadb.com created the issue
In computing node's config file, set ha_mode for metadata cluster. Also the same 3 modes as for storage shards. only do MGR related work when ha_mode is mgr.
We did it differently --- ha_mode is a kunlun cluster wide property now, and stored in the cluster's row in db_clusters table.
Also, a metadata shard must be of same ha_mode with all kunlun clusters registered into it.
This is so because ha_mode is actually in practice a global setting --- it's only no_rep on clouds, and mgr/rbr in on premise deployments.
Issue migrated from trac ticket # 181 www.kunlunbase.com
component: computing nodes | priority: major | resolution: finished
2021-09-27 19:10:05: zhaowei@zettadb.com created the issue