John Spray 56171cbe8c pageserver: more permissive activation timeout when testing (#6564) ...

## Problem

The 5 second activation timeout is appropriate for production
environments, where we want to give a prompt response to the cloud
control plane, and if we fail it will retry the call. In tests however,
we don't want every call to e.g. timeline create to have to come with a
retry wrapper.

This issue has always been there, but it is more apparent in sharding
tests that concurrently attach several tenant shards.

Closes: https://github.com/neondatabase/neon/issues/6563

## Summary of changes

When `testing` feature is enabled, make `ACTIVE_TENANT_TIMEOUT` 30
seconds instead of 5 seconds.

2024-02-02 15:14:42 +01:00

..

benches

pageserver: make walredo shard-aware

2024-01-03 14:22:40 +00:00

client

Download SLRU segments on demand (#6151)

2024-01-31 21:39:18 +02:00

ctl

integrate tokio-epoll-uring as alternative VirtualFile IO engine (#5824)

2024-01-26 09:25:07 +01:00

pagebench

pagebench: fix percentiles reporting (#6547)

2024-01-31 23:29:48 +00:00

src

pageserver: more permissive activation timeout when testing (#6564)

2024-02-02 15:14:42 +01:00

test_data

Add walingest test (#5892)

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

Cargo.toml

feat(walredo): use posix_spawn by moving close_fds() work to walredo C code (#6574)

2024-02-01 22:38:34 +01:00