25-4-1: schemeshard: add batch processing for ttl responses#34445
25-4-1: schemeshard: add batch processing for ttl responses#34445ijon wants to merge 3 commits intoydb-platform:stable-25-4-1from
Conversation
Changes: - Add size- and time- based batching for `TEvConditionalEraseRowsResponse`. `TTxScheduleConditionalErase` now processes batches instead of individual responses. - Process `TEvConditionalEraseRowsResponse::PARTIAL` response early, without entering a local transaction. - Also move TSchemeShardConfig from `config.proto` to separate `schemeshard_config.proto`. Configuration: - `feature_flags.enable_conditional_erase_response_batching` — enables batching - `schemeshard_config.cond_erase_response_batch_size` — batch size limit - default: 100 - zero disables batching - `schemeshard_config.cond_erase_response_batch_max_time_ms` — max pending batch time - default: 100 ms - value clamped between 1-1000 ms
Make table checks once per table, not once per shard.
|
🟢 |
Run Extra TestsRun additional tests for this PR. You can customize:
|
|
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪ ⚪ DetailsYa make output | Test bloat | Test bloat
⚪ Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
2 participants
Cherry-pick from
main:Changes:
TEvConditionalEraseRowsResponse.TTxScheduleConditionalErasenow processes batches instead of individual responses.TEvConditionalEraseRowsResponse::PARTIALresponse early, without entering a local transaction.