walshadow: stopping flushing partial segment reason="signal" out_dir=/var/lib/walshadow/out
Maintainers usually reply within 1 day
@harshil-goel is already working on this.
Since Sep 9, 2026.
Assessment
This issue has not been assessed yet.
Description
Sep 09 00:01:59 ip-10-130-0-181 walshadow-run[2276]: 2026-09-09T00:01:59.422767Z INFO walshadow: status segments_shipped=2 last_lsn="0/23000000" shadow_apply="0/220002D0" source_ahead_bytes=16777216 metrics=total=13 xlog/to_shadow=7 xact/to_shadow=1 standby/to_shadow=3 heap/to_decoder=2 kept=11 dropped=2 relmap_updates=0 pg_class_undecoded=0 pg_class_oid_in_prefix=0 decoder=de>
Sep 09 00:02:00 ip-10-130-0-181 walshadow-run[2276]: 2026-09-09T00:02:00.735813Z INFO walshadow: status segments_shipped=3 last_lsn="0/24000000" shadow_apply="0/24000000" source_ahead_bytes=16777216 metrics=total=18 xlog/to_shadow=11 xact/to_shadow=1 standby/to_shadow=4 heap/to_decoder=2 kept=16 dropped=2 relmap_updates=0 pg_class_undecoded=0 pg_class_oid_in_prefix=0 decoder=d>
Sep 09 00:02:07 ip-10-130-0-181 walshadow-run[2276]: 2026-09-09T00:02:07.523310Z INFO walshadow::config: reload diff applied pending=0 applied=3
Sep 09 00:02:20 ip-10-130-0-181 walshadow-run[2276]: 2026-09-09T00:02:20.177268Z INFO walshadow: stopping — flushing partial segment reason="signal" out_dir=/var/lib/walshadow/out
Sep 09 00:02:20 ip-10-130-0-181 systemd[1]: Stopping walshadow catalog-replay daemon...
Sep 09 00:02:20 ip-10-130-0-181 walshadow-run[2276]: 2026-09-09T00:02:20.185238Z WARN walshadow: walsender connection ended error=server: protocol: client sent Terminate
Sep 09 00:02:20 ip-10-130-0-181 systemd[1]: walshadow.service: Deactivated successfully.
Sep 09 00:02:20 ip-10-130-0-181 systemd[1]: Stopped walshadow catalog-replay daemon.
Sep 09 00:02:20 ip-10-130-0-181 systemd[1]: walshadow.service: Consumed 4.385s CPU time.
- Dominant language
- Rust
- Stars
- 249
- Forks
- 13
- Avg merge
- 23h 4m
- Merged PRs (30d)
- 59
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ClickHouse/walshadow
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
ClickHouse/walshadow#277 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
ClickHouse/walshadow#275 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ClickHouse/walshadow#223 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ClickHouse/walshadow#178 ·
Maintainers usually reply within 1 day
-
Remove _xidMay be free again @harshil-goel claimed this 62 days ago, and no pull request is open. Open
ClickHouse/walshadow#115 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in ClickHouse/walshadow
Similar issues
-
docs(metrics): replace stale src/metrics.rs line anchors in dashboard-metrics.md with symbol namesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
ci-cd desktop size:low telemetry-improvement telemetry-round-1
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vfarcic/dot-agent-deck#2079 ·
Maintainers usually reply within 1 day
-
enhancement user-priority/P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days