Error during DuckDB node deployment

[shawn0915]

安装这个步骤来的，
https://github.com/alibaba/AliSQL/blob/master/wiki/duckdb/how-to-setup-duckdb-node-zh.md

初始化的时候报错了，

[shawnyan@rl9 ~]$ ./init_alisql_dir.sh $HOME/alisql_8044
Initializing AliSQL directories at: /home/shawnyan/alisql_8044
OK: Directory structure created.
Config file: /home/shawnyan/alisql_8044/alisql.cnf
[shawnyan@rl9 ~]$ ./alisql/bin/mysqld --defaults-file=$HOME/alisql_8044/alisql.cnf --initialize-insecure
[shawnyan@rl9 ~]$ ./alisql/bin/mysqld_safe --defaults-file=$HOME/alisql_8044/alisql.cnf &
[1] 70335
[shawnyan@rl9 ~]$ 2026-02-05T09:45:33.125152Z mysqld_safe Logging to '/home/shawnyan/alisql_8044/log/mysql/error.log'.
2026-02-05T09:45:33.151854Z mysqld_safe Starting mysqld daemon with databases from /home/shawnyan/alisql_8044/data/dbs
2026-02-05T09:45:35.120438Z mysqld_safe mysqld from pid file /home/shawnyan/alisql_8044/run/mysqld.pid ended

[1]+  Done                    ./alisql/bin/mysqld_safe --defaults-file=$HOME/alisql_8044/alisql.cnf
[shawnyan@rl9 ~]$ cat /home/shawnyan/alisql_8044/log/mysql/error.log
2026-02-05T09:45:20.680349Z 0 [Warning] [MY-011068] [Server] The syntax '--ssl=off' is deprecated and will be removed in a future release. Please use --tls-version='' instead.
2026-02-05T09:45:20.680373Z 0 [Warning] [MY-011070] [Server] 'binlog_format' is deprecated and will be removed in a future release.
2026-02-05T09:45:20.680482Z 0 [System] [MY-013169] [Server] /home/shawnyan/alisql/bin/mysqld (mysqld 8.0.44-alisql-dev) initializing of server in progress as process 70292
2026-02-05T09:45:20.689286Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-02-05T09:45:20.884539Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
query:INSERT INTO mysql.duckdb_binlog_position VALUES('mysql-bin.000001', 157)
2026-02-05T09:45:21.416874Z 0 [ERROR] [MY-013236] [Server] The designated data directory /home/shawnyan/alisql_8044/data/dbs/ is unusable. You can remove all files that the server added to it.
2026-02-05T09:45:21.416893Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-02-05T09:45:22.953887Z 0 [System] [MY-010910] [Server] /home/shawnyan/alisql/bin/mysqld: Shutdown complete (mysqld 8.0.44-alisql-dev)  Source distribution.
2026-02-05T09:45:33.125152Z mysqld_safe Logging to '/home/shawnyan/alisql_8044/log/mysql/error.log'.
2026-02-05T09:45:33.151854Z mysqld_safe Starting mysqld daemon with databases from /home/shawnyan/alisql_8044/data/dbs
2026-02-05T09:45:33.366962Z 0 [Warning] [MY-011068] [Server] The syntax '--ssl=off' is deprecated and will be removed in a future release. Please use --tls-version='' instead.
2026-02-05T09:45:33.366985Z 0 [Warning] [MY-011070] [Server] 'binlog_format' is deprecated and will be removed in a future release.
2026-02-05T09:45:33.367094Z 0 [System] [MY-010116] [Server] /home/shawnyan/alisql/bin/mysqld (mysqld 8.0.44-alisql-dev) starting as process 70625
2026-02-05T09:45:33.374210Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-02-05T09:45:33.483233Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
mysqld: Table 'mysql.plugin' doesn't exist
2026-02-05T09:45:33.558686Z 0 [ERROR] [MY-010735] [Server] Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.
2026-02-05T09:45:33.558939Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559020Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559082Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559194Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559452Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559527Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559585Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.559633Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2026-02-05T09:45:33.621215Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2026-02-05T09:45:33.678916Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
query:INSERT INTO mysql.duckdb_binlog_position VALUES('mysql-bin.000002', 157)
2026-02-05T09:45:33.680321Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-02-05T09:45:35.091030Z 0 [System] [MY-010910] [Server] /home/shawnyan/alisql/bin/mysqld: Shutdown complete (mysqld 8.0.44-alisql-dev)  Source distribution.
2026-02-05T09:45:35.120438Z mysqld_safe mysqld from pid file /home/shawnyan/alisql_8044/run/mysqld.pid ended
[shawnyan@rl9 ~]$

[a664078163]

删掉重新来一遍就好了，大概率是第一次执行出错
rm -rf $HOME/alisql_8044
./init_alisql_dir.sh $HOME/alisql_8044

如果已经启动好了，记得先停掉
alisql/bin/mysqladmin -uroot --socket=$HOME/alisql_8044/run/mysql.sock shutdown -p

[shawn0915]

@a664078163 正常启动可以，但是打开duckdb mode就启动报错

query:INSERT INTO mysql.duckdb_binlog_position VALUES('mysql-bin.000004', 197)
2026-02-05T12:54:44.198917Z 0 [ERROR] [MY-010119] [Server] Aborting

[a664078163]

@a664078163 正常启动可以，但是打开duckdb mode就启动报错

query:INSERT INTO mysql.duckdb_binlog_position VALUES('mysql-bin.000004', 197)
2026-02-05T12:54:44.198917Z 0 [ERROR] [MY-010119] [Server] Aborting

你是按照方式1从零开始构建 DuckDB 实例部署的吗？配置文件有修改吗？log里有更详细的错误信息吗？

[shawn0915]

@a664078163 就是按照readme一步步来，然后就报错。难道是os太新了？

[mysql@rl9 ~]$ cat /etc/redhat-release
Rocky Linux release 9.7 (Blue Onyx)
[mysql@rl9 ~]$ uname -a
Linux rl9.shawnyan.cn 5.14.0-611.24.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jan 23 11:42:43 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux


git clone https://github.com/alibaba/AliSQL.git
cd AliSQL

# Build (release mode)
sh build.sh -t release -d ~/alisql

# Install
make install

[mysql@rl9 ~]$ ./init_alisql_dir.sh $HOME/alisql_8044
OK: created /home/mysql/alisql_8044 and /home/mysql/alisql_8044/alisql.cnf

-- alisql.cnf 注释掉 duckdb 的参数，可以正常初始化启动
-- 但是保留，就不行

[mysql@rl9 ~]$ ./alisql/bin/mysqld --defaults-file=$HOME/alisql_8044/alisql.cnf --initialize-insecure

2026-02-05T12:54:17.455179Z mysqld_safe Starting mysqld daemon with databases from /home/mysql/alisql_8044/data/dbs
2026-02-05T12:54:17.646863Z 0 [Warning] [MY-011068] [Server] The syntax '--ssl=off' is deprecated and will be removed in a future release. Please use --tls-version='' instead.
2026-02-05T12:54:17.646883Z 0 [Warning] [MY-011070] [Server] 'binlog_format' is deprecated and will be removed in a future release.
2026-02-05T12:54:17.646976Z 0 [System] [MY-010116] [Server] /home/mysql/alisql/bin/mysqld (mysqld 8.0.44-alisql-dev) starting as process 132972
2026-02-05T12:54:17.663175Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-02-05T12:54:17.751582Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
query:INSERT INTO mysql.duckdb_binlog_position VALUES('mysql-bin.000003', 197)
2026-02-05T12:54:17.902223Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-02-05T12:54:19.440774Z 0 [System] [MY-010910] [Server] /home/mysql/alisql/bin/mysqld: Shutdown complete (mysqld 8.0.44-alisql-dev)  Source distribution.

[p1p1bear]

@shawn0915 使用的是源码编译的还是安装包中alisql 初始化和拉起的呢？

[shawn0915]

@p1p1bear 你好，源码编译，就当前最新代码，readme里这个步骤。

git clone https://github.com/alibaba/AliSQL.git
cd AliSQL

# Build (release mode)
sh build.sh -t release -d ~/alisql

# Install
make install

[p1p1bear]

@shawn0915 好的，我这边尝试分析下。

[fkpwolf]

我也有同样问题。在Rocky 8 Container环境用rpm安装包也是不行，感觉和 kernel 版本有关。Rocky 8 VM下面正常。

[p1p1bear]

Hi @a664078163 @fkpwolf @shawn0915
Thanks for your attention. We’ve narrowed this down to an exception happening during DuckDB initialization on a specific OS.

The backtrace is:

(gdb) bt
#0  Binlog_ext::duckdb_binlog_rotate (this=0xf67d340 <mysql_bin_log_ext>) at /home/songhuaxiong.shx/huaxiong.shx/code/AliSQL/sql/binlog_ext.cc:196
#1  0x0000000005d38d58 in mysqld_main (argc=23, argv=0xfc7d070) at /home/songhuaxiong.shx/huaxiong.shx/code/AliSQL/sql/mysqld.cc:8055
#2  0x0000000005d268a6 in main (argc=3, argv=0x7fffffffd6c8) at /home/songhuaxiong.shx/huaxiong.shx/code/AliSQL/sql/main.cc:26

At line 196, I observed a DuckDB query execution error indicating an out-of-memory condition:

(gdb) p query_res.get()->error
$5 = {initialized = true, type = duckdb::ExceptionType::OUT_OF_MEMORY,
  raw_message = "could not allocate block of size 256.0 KiB (0 bytes/0 bytes used)\n\nPossible solutions:\n* Reducing the number of threads (SET threads=X)\n* Disabling insertion-order preservation (SET preserve_insertion"...,
  final_message = "Out of Memory Error: could not allocate block of size 256.0 KiB (0 bytes/0 bytes used)\n\nPossible solutions:\n* Reducing the number of threads (SET threads=X)\n* Disabling insertion-order preservation (S"..., extra_info = std::unordered_map with 0 elements}

In our setup, when duckdb_memory_limit = 0, DuckDB is expected to automatically pick a default memory limit based on the system. It looks like something goes wrong during this auto-detection step on that OS.

A quick workaround is to explicitly set duckdb_memory_limit in the generated alisql.cnf (e.g. 2G), which avoids the automatic selection and prevents the issue:

- duckdb_memory_limit=0
+ duckdb_memory_limit=2147483648

My initial guess is that DuckDB’s default memory limit selection may differ across operating systems. We’ll continue investigating and will share more details once we have them. :)