• Joined on 2026-04-07
dailz closed issue dailz/go-kv#16 2026-06-12 08:52:47 +08:00
设计审查: Segment ID 连续性要求与旧 segment 删除后的 gap 处理
dailz closed issue dailz/go-kv#15 2026-06-12 08:39:26 +08:00
设计审查: WAL segment 大小未定义,最大 batch 可能无法写入空 segment
dailz opened issue dailz/go-kv#21 2026-06-12 08:28:49 +08:00
设计审查: Get API 必须返回 found 状态以支持空值确认约束
dailz opened issue dailz/go-kv#20 2026-06-12 08:28:42 +08:00
设计审查: Periodic/Never 落盘策略下 fsync 错误的上报机制
dailz opened issue dailz/go-kv#19 2026-06-12 08:28:34 +08:00
设计审查: WAL 内部缓冲模型 — 私有 encode buffer vs 共享 buffered writer
dailz opened issue dailz/go-kv#18 2026-06-12 08:28:24 +08:00
设计审查: publishedSequence 的范围 — 物理 mutation 还是包含 MVCC commit record
dailz opened issue dailz/go-kv#17 2026-06-12 08:28:17 +08:00
设计审查: MANIFEST 职责边界 — checkpoint vs WAL 恢复终点
dailz opened issue dailz/go-kv#16 2026-06-12 08:28:10 +08:00
设计审查: Segment ID 连续性要求与旧 segment 删除后的 gap 处理
dailz opened issue dailz/go-kv#15 2026-06-12 08:28:03 +08:00
设计审查: WAL segment 大小未定义,最大 batch 可能无法写入空 segment
dailz closed issue dailz/go-kv#14 2026-06-11 20:36:15 +08:00
[Important] publishedSequence 需要明确的内存序约束
dailz closed issue dailz/go-kv#13 2026-06-11 20:27:18 +08:00
[Important] Batch 校验缺少资源上限
dailz closed issue dailz/go-kv#12 2026-06-11 20:17:59 +08:00
[Important] 尾部截断后缺少持久化步骤
dailz closed issue dailz/go-kv#11 2026-06-11 20:09:55 +08:00
[Important] CURRENT 文件权威性与实际恢复模型不一致
dailz pushed to main at dailz/go-kv 2026-06-11 19:54:20 +08:00
5e9836c931 update MemTable arena reservation design
b037c1a382 update MemTable publish ordering design
a98c144c51 update WAL write failure design
f6a2cd979e update WAL segment boundary design
Compare 4 commits »
dailz closed issue dailz/go-kv#10 2026-06-11 19:53:25 +08:00
[Important] MemTable 写入失败(Arena 满)在 WAL 写入后未覆盖
dailz closed issue dailz/go-kv#9 2026-06-11 18:30:07 +08:00
[Critical] Go 内存模型:lock-free read 需要原子发布机制
dailz closed issue dailz/go-kv#8 2026-06-11 18:15:21 +08:00
[Critical] 恢复后未确认 Batch 可能变成已发布
dailz commented on issue dailz/go-kv#7 2026-06-11 17:52:59 +08:00
[Critical] 预创建 segment 可破坏尾部截断逻辑

已在设计文档中修复:f6a2cd9 update WAL segment boundary design 补充了 segment rotation 约束,明确新 segment 的 durable-ready 协议只能在当前 active segment 已结束于完整 WAL Batch 边界后启动,并禁…

dailz closed issue dailz/go-kv#7 2026-06-11 17:52:35 +08:00
[Critical] 预创建 segment 可破坏尾部截断逻辑
dailz closed issue dailz/go-kv#6 2026-06-11 17:33:52 +08:00
[Critical] Segment 边界跨 Batch 行为未定义