Aleksandr Sarantsev 4559ba79b6 Introduce force flag for new deletion API (#12588) ...

## Problem

The force deletion API should behave like the graceful deletion API - it
needs to support cancellation, persistence, and be non-blocking.

## Summary of Changes

- Added a `force` flag to the `NodeStartDelete` command.
- Passed the `force` flag through the `start_node_delete` handler in the
storage controller.
- Handled the `force` flag in the `delete_node` function.
- Set the tombstone after removing the node from memory.
- Minor cleanup, like adding a `get_error_on_cancel` closure.

---------

Co-authored-by: Aleksandr Sarantsev <aleksandr.sarantsev@databricks.com>

2025-07-17 11:51:31 +00:00

..

client

storcon + safekeeper + scrubber: propagate root CA certs everywhere (#11418)

2025-04-04 06:30:48 +00:00

migrations

Add new activating scheduling policy for safekeepers (#12441)

2025-07-03 16:27:43 +00:00

src

Introduce force flag for new deletion API (#12588)

2025-07-17 11:51:31 +00:00

Cargo.toml

pageserver: add gRPC LSN lease support (#12384)

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