Arseny Sher 98e18e9a54 Add s3 storage to test_s3_wal_replay (#10809) ...

## Problem

The test is flaky: WAL in remote storage appears to be corrupted. One of
hypotheses so far is that corruption is the result of local fs
implementation being non atomic, and safekeepers may concurrently PUT
the same segment. That's dubious though because by looking at local_fs
impl I'd expect then early EOF on segment read rather then observed
zeros in test failures, but other directions seem even less probable.

## Summary of changes

Let's add s3 backend as well and see if it is also flaky. Also add some
more logging around segments uploads.

ref https://github.com/neondatabase/neon/issues/10761

2025-02-13 18:05:15 +00:00

..

benches

pageserver,safekeeper: increase heap profiling frequency to 2 MB (#10362)

2025-01-13 09:44:59 +00:00

client

storcon: track safekeepers in memory, send heartbeats to them (#10583)

2025-02-13 11:06:30 +00:00

spec

TLA+ spec for safekeeper membership change (#9966)

2025-01-09 12:26:17 +00:00

src

Add s3 storage to test_s3_wal_replay (#10809)

2025-02-13 18:05:15 +00:00

tests

Add START_WAL_PUSH proto_version and allow_timeline_creation options. (#10406)

2025-01-16 08:01:19 +00:00

Cargo.toml

Split utils::http to separate crate (#10753)

2025-02-11 22:06:53 +00:00