Alexey Kondratov 53a05e8ccb fix(compute_ctl): Only offload LFC state if no prewarming is in progress (#12645) ...

## Problem

We currently offload LFC state unconditionally, which can cause
problems. Imagine a situation:
1. Endpoint started with `autoprewarm: true`.
2. While prewarming is not completed, we upload the new incomplete
state.
3. Compute gets interrupted and restarts.
4. We start again and try to prewarm with the state from 2. instead of
the previous complete state.

During the orchestrated prewarming, it's probably not a big issue, but
it's still better to do not interfere with the prewarm process.

## Summary of changes

Do not offload LFC state if we are currently prewarming or any issue
occurred. While on it, also introduce `Skipped` LFC prewarm status,
which is used when the corresponding LFC state is not present in the
endpoint storage. It's primarily needed to distinguish the first compute
start for particular endpoint, as it's completely valid to do not have
LFC state yet.

2025-07-17 21:43:43 +00:00

..

src

fix(compute_ctl): Only offload LFC state if no prewarming is in progress (#12645)

2025-07-17 21:43:43 +00:00

tests

offload_lfc_interval_seconds in ComputeSpec (#12447)

2025-07-04 18:49:57 +00:00

Cargo.toml

pageserver: add gRPC LSN lease support (#12384)

2025-06-30 12:44:17 +00:00