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-01-17 15:44:57: zhangjindong@zettadb.com created the issue
[kunlun@kunlun-test6 onesharddata]$ pg_ctl -D pwd/pgdatadir init
The files belonging to this database system will be owned by user "kunlun".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /home/kunlun/onesharddata/pgdatadir ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Asia/Shanghai
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... 2022-01-17 15:39:10.569 CST [3976830] FATAL: could not open relation with OID 3329
backtrace:
stack_bottom = 0 thread_stack 0x200000
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(get_stacktrace_str+0x4b) [0x90e54c]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(elog_finish+0x1af) [0xa7a889]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(relation_open+0x8a) [0x4e3e50]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(TrackTemporaryTarget+0x28) [0x57543c]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(ExecuteGrantStmt+0xf0) [0x598437]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres() [0x90c16d]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(standard_ProcessUtility+0xba9) [0x90a7fc]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(ProcessUtility+0xef) [0x909c4c]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres() [0x908b80]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres() [0x908e30]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(PortalRun+0x314) [0x9082d3]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres() [0x902034]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(PostgresMain+0x82e) [0x9063f8]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres(main+0x2d9) [0x76b325]
/lib64/libc.so.6(__libc_start_main+0xf3) [0x7f78028ae493]
/home/kunlun/oneshardbase/kunlun-server-0.9.1/bin/postgres() [0x480949]
2022-01-17 15:39:10.569 CST [3976830] STATEMENT: REVOKE ALL on pg_file_settings FROM PUBLIC;
REVOKE EXECUTE ON FUNCTION pg_show_all_file_settings() FROM PUBLIC;
child process exited with exit code 1
initdb: removing contents of data directory "/home/kunlun/onesharddata/pgdatadir"
pg_ctl: database system initialization failed
insert OID = 3329 ( pg_show_all_file_settings 11 10 12 1 1000 0 0 f f f t t v s 0 0 2249 "" "{25,23,23,25,25,16,25}" "{o,o,o,o,o,o,o}" "{sourcefile,sourceline,seqno,name,setting,applied,error}" nullnull show_all_file_settings nullnullnull )
jd-zhang
commented
2 years ago
Issue migrated from trac ticket # 411
component: computing nodes | priority: blocker | resolution: fixed
2022-01-17 15:44:57: zhangjindong@zettadb.com created the issue