jeremyhi b30d17f89c docs: align wal.sync_period documented default with actual fallback (5s) (#8753) ...

The example TOMLs and generated config.md documented the default of
wal.sync_period as "10s", but since #5677 moved the WAL sync task to a
background RepeatedTask, an unset sync_period falls back to 5s in
RaftEngineLogStore. The two paths therefore had different fsync
periods: deployments based on the example configs used 10s while bare
configs used 5s.

Align the documentation with the actual code behavior (5s) instead of
changing the code fallback to 10s, so that no existing deployment
silently gets a larger data-loss window on host power loss.

- config/datanode.example.toml, config/standalone.example.toml: 10s -> 5s
- config/config.md: regenerated via make config-docs
- src/cmd/tests/load_config_test.rs: update assertions accordingly

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

2026-08-05 08:56:55 +00:00

..

config-docs-template.md

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

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

config.md

docs: align wal.sync_period documented default with actual fallback (5s) (#8753)

2026-08-05 08:56:55 +00:00

datanode.example.toml

docs: align wal.sync_period documented default with actual fallback (5s) (#8753)

2026-08-05 08:56:55 +00:00

flownode.example.toml

feat(logging): add enable_file_logging option to disable file logging (#8721)

2026-08-03 12:01:08 +00:00

frontend.example.toml

refactor!: move native histogram config and prom_validation_mode to prom_store (#8744)

2026-08-05 06:16:09 +00:00

metasrv.example.toml

chore!: gate soft-drop table behind the enterprise feature (#8747)

2026-08-05 04:28:30 +00:00

standalone.example.toml

docs: align wal.sync_period documented default with actual fallback (5s) (#8753)

2026-08-05 08:56:55 +00:00