Arpad Müller 0d3d639ef3 storcon: remove timeouts for safekeeper heartbeating (#11232) ...

PRs #10891 and #10902 have time-bounded the safekeeper heartbeating of
the storage controller. Those timeouts were not meant to be permanent,
but temporary until we figured out the reasons for the safekeeper
heartbeating causing problems.

Now they are better understood and resolved. A comment is
[here](https://github.com/neondatabase/cloud/issues/24396#issuecomment-2679342929),
but most importantly, we've had:

* #10954 to send heartbeats concurrently (before the issue was we sent
them sequentially, so the total time time was number of nodes times time
for timeout to be hit, now the total time is the maximum of all things
we are heartbeating)
* work to actually make heartbeats work and not error, i.e. JWT rollout
for storcon, not sending heartbeats to decomissioned safekeepers,
removal of decomissioned safekeepers from the databases

Part of https://github.com/neondatabase/cloud/issues/25473

2025-03-18 03:37:45 +00:00

..

client

Migrate the last crates to edition 2024 (#10998)

2025-02-27 09:40:40 +00:00

migrations

storcon: timetime table, creation and deletion (#11058)

2025-03-11 02:31:22 +00:00

src

storcon: remove timeouts for safekeeper heartbeating (#11232)

2025-03-18 03:37:45 +00:00

Cargo.toml

storcon: timetime table, creation and deletion (#11058)

2025-03-11 02:31:22 +00:00