jeremyhi 70a0c826ca docs(config): qualify when the object store WAL batch seals on size (#9538) ...

The `wal.flush_interval` comment claimed that under sustained load the
batch always seals on `max_batch_bytes` and the interval no longer
matters. Sustained-load runs on S3 sealed on the timer in every case
because the admitted bytes did not reach `max_batch_bytes` within one
interval. State the actual condition: the batch seals on size only when
the admitted bytes reach `max_batch_bytes` before the next timer tick;
otherwise it seals on the timer, whatever the load.

Regenerated `config/config.md` from the example TOMLs.

Signed-off-by: jeremyhi <fengjiachun@gmail.com>

2026-10-12 11:16:53 +00:00

..

config-docs-template.md

feat: make flow distributed work&tests (#4256)

2024-07-05 14:46:44 +00:00

config.md

docs(config): qualify when the object store WAL batch seals on size (#9538)

2026-10-12 11:16:53 +00:00

datanode.example.toml

docs(config): qualify when the object store WAL batch seals on size (#9538)

2026-10-12 11:16:53 +00:00

flownode.example.toml

docs(config): align example configs and config.md with actual defaults (#9460)

2026-10-08 07:23:22 +00:00

frontend.example.toml

perf: cache OTLP trace service and operation writes (#9432)

2026-10-10 02:45:43 +00:00

metasrv.example.toml

docs(config): align example configs and config.md with actual defaults (#9460)

2026-10-08 07:23:22 +00:00

standalone.example.toml

docs(config): qualify when the object store WAL batch seals on size (#9538)

2026-10-12 11:16:53 +00:00