You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m investigating the checkpoint retry path in EndConversationWorkspaceUseAsync and will work on a narrow fix if a regression reproduces it: bound repeated save attempts while preserving recovery from a temporarily busy runner gate, normal deferred retry, and foreground lease supersession.
The 100 ms retry is a lead, not yet proof of the reported binlog volume. I’ll trace where compression/chunk writes occur and include failure/recovery tests before proposing a change. This does not claim the separate Compose/MySQL binlog configuration request or the entire issue.
Expectation 2 from this issue — bound (or disable) binary logging in the default Compose stack — is now a PR: #1196. It starts the bundled mysql:8.4 with --binlog-expire-logs-seconds=86400 and --max-binlog-size=67108864 so a write storm cannot fill loopforge_mysql-data with binlogs, documents raising/removing the flags for point-in-time recovery or replication (and --skip-log-bin for single-node evaluation), and documents the PURGE BINARY LOGS + SET PERSIST binlog_expire_logs_seconds recovery for existing stacks.
A local data point from a Compose deployment: on v0.4.1-rc.1 the volume accumulated 1.18 GB of binlogs in about a day while the database tables stayed under 40 MB — not the 1.2–9.7 MB/s storm reported above, but the same unbounded-log shape. Purged it with the mitigation from this issue (FLUSH BINARY LOGS, PURGE BINARY LOGS TO <current>, SET PERSIST binlog_expire_logs_seconds=259200) and loopforge_mysql-data dropped from 1.53 GB to 0.36 GB.
The engine-side retry/lease work is separate (#1148 explicitly notes it does not change MySQL/Compose configuration).
Activity
cocofhu00 commentedon Nov 20, 2026
感谢反馈。
我的理解是:自托管的 LoopForge 0.4.0 在使用 agent workspace 之后,checkpoint 会反复进入「保存 → 校验 → 恢复」且停不下来,platform 持续大量写入,并连带把 MySQL binlog 撑到大约 298GB。
已经看到这条 Issue,会按现有 Issue 排期查看。
wcy12378 commentedon Nov 20, 2026
I’m investigating the checkpoint retry path in
EndConversationWorkspaceUseAsyncand will work on a narrow fix if a regression reproduces it: bound repeated save attempts while preserving recovery from a temporarily busy runner gate, normal deferred retry, and foreground lease supersession.The 100 ms retry is a lead, not yet proof of the reported binlog volume. I’ll trace where compression/chunk writes occur and include failure/recovery tests before proposing a change. This does not claim the separate Compose/MySQL binlog configuration request or the entire issue.
linus-liu-web commentedon Nov 21, 2026
Expectation 2 from this issue — bound (or disable) binary logging in the default Compose stack — is now a PR: #1196. It starts the bundled
mysql:8.4with--binlog-expire-logs-seconds=86400and--max-binlog-size=67108864so a write storm cannot fillloopforge_mysql-datawith binlogs, documents raising/removing the flags for point-in-time recovery or replication (and--skip-log-binfor single-node evaluation), and documents thePURGE BINARY LOGS+SET PERSIST binlog_expire_logs_secondsrecovery for existing stacks.A local data point from a Compose deployment: on v0.4.1-rc.1 the volume accumulated 1.18 GB of binlogs in about a day while the database tables stayed under 40 MB — not the 1.2–9.7 MB/s storm reported above, but the same unbounded-log shape. Purged it with the mitigation from this issue (
FLUSH BINARY LOGS,PURGE BINARY LOGS TO <current>,SET PERSIST binlog_expire_logs_seconds=259200) andloopforge_mysql-datadropped from 1.53 GB to 0.36 GB.The engine-side retry/lease work is separate (#1148 explicitly notes it does not change MySQL/Compose configuration).