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.
2021-09-22 11:22:30: @david-zhao created the issue
if a UPDATE or DELETE statement executed in a storage shard's txn branch modifies no rows, the txn branch can simply be committed in one phase and it can be seen as read only, although it's marked written.
2021-09-22 11:34:23: @david-zhao changed title from distributed transaction 2pc --- txn write status incorrectly classified to distributed transaction 2pc --- txn write status incorrectly classified for shards with zero modified rows
jd-zhang
commented
3 years ago
Issue migrated from trac ticket # 164
component: computing nodes | priority: major
2021-09-22 11:22:30: @david-zhao created the issue