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.
2022-03-07 17:49:31: zhaowei@zettadb.com created the issue
We can lower wal_level to 'minimal' because in Kunlun distributed database cluster we don't need pg's WAL archiving or pg's stream replication features.
the default 'replica' level produces WAL even in read only workloads, which is totally redundant for kunlun.
minimal level can guarantee crash safety, that's all we need from a kunlun computing node's WAL.
We do logical dump to backup a computing node and replay DDL log to catch up, so WAL archiving is totally avoided.
Modify below vars in config template to do so:
wal_level=minimal
max_wal_senders=0
jd-zhang
commented
2 years ago
Issue migrated from trac ticket # 465 www.kunlunbase.com
component: computing nodes | priority: major
2022-03-07 17:49:31: zhaowei@zettadb.com created the issue