Christian Schwarz 7403d55013 walredo: stderr cleanup & make explicitly cancel safe (#6031) ...

# Problem

I need walredo to be cancellation-safe for
https://github.com/neondatabase/neon/pull/6000#discussion_r1412049728

# Solution

We are only `async fn` because of
`wait_for(stderr_logger_task_done).await`, added in #5560 .

The `stderr_logger_cancel` and `stderr_logger_task_done` were there out
of precaution that the stderr logger task might for some reason not stop
when the walredo process terminates.
That hasn't been a problem in practice.
So, simplify things:
- remove `stderr_logger_cancel` and the
`wait_for(...stderr_logger_task_done...)`
- use `tokio::process::ChildStderr` in the stderr logger task
- add metrics to track number of running stderr logger tasks so in case
I'm wrong here, we can use these metrics to identify the issue (not
planning to put them into a dashboard or anything)

2023-12-04 16:06:41 +00:00

..

benches

pageserver: refactor TenantId to TenantShardId in Tenant & Timeline (#5957)

2023-11-29 14:52:35 +00:00

ctl

pagectl: add subcommand to rewrite layer file summary (#5933)

2023-11-30 11:34:30 +00:00

src

walredo: stderr cleanup & make explicitly cancel safe (#6031)

2023-12-04 16:06:41 +00:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

refactor: use serde for TenantConf deserialization Fixes: #5300 (#5310)

2023-11-30 12:47:13 +02:00