Open heni02 opened 10 months ago
The likely cause of the MO crash is due to OOM. Need find the cause for the OOM.
1、似乎测试脚本有点问题。连接到MO会报这个错
{"level":"ERROR","time":"2024/01/03 14:52:16.668663 +0800","caller":"frontend/mysql_cmd_executor.go:315","msg":"error: SQL parser error: You have an error in your SQL syntax; check the manual that corresponds to your MatrixOne server version for the right syntax to use. syntax error at line 1 column 9 near \" $$\";","span":{"trace_id":"f33dd58e-cd53-8a52-58e4-f29d4991fc2c","span_id":"164f42c1b6b06b08"}}
2、但不知道为啥会引起服务器后来出错了。应该跟1关系不太大
no process
no process
no process
no process
no process
才留意说的是on duplicate key 算子。 该算子会把数据一致保存在内存中,直到所有数据都被检验一遍,所以大数据量的时候很容易OOM。 得等spill完成后才不会OOM
1.2估计做不了spill 暂无安排
暂无具体安排。
目前的计划是给某些算子增加process级别的mpool not enough的检测。避免crash的发生。
等Join的spill再转送该issue。
spill需要延期到2.1,2.0.1无法完成开发。
no words.
不确定具体是什么导致的oom, 2.1完成spill后再进行验证。
同上
Is there an existing issue for the same bug?
Branch Name
main
Commit ID
4531180d4b20c179baa426cca179aaebc70cec84
Other Environment Information
Actual Behavior
原表数据量为1050万有主键,并发100,刚开始执行mo 挂掉了,但数据量为1050万无主键并发100测试mo正常 sql:insert into table_1000w(clo4) values({tbx}) on duplicate key update clo2=clo2/10;
试了下创建简单的表,该sql执行成功
mo log:
mo_log.tar.gz
Expected Behavior
No response
Steps to Reproduce
Additional information
No response