[
https://issues.apache.org/jira/browse/CASSANDRA-18500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18500:
------------------------------------------
Test and Documentation Plan:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2321]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2890/workflows/3702a648-179c-4536-b004-bd8297c34a53]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2890/workflows/301bdae4-0683-40d1-8939-6a2d2ac0edcb]|
Status: Patch Available (was: Open)
> Add guardrail for partition size
> --------------------------------
>
> Key: CASSANDRA-18500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18500
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add a guardrail for max partition size, for example:
> {code:java}
> partition_size_warn_threshold: 50MiB
> partition_size_fail_threshold: 100MiB
> {code}
> Most probably this guardrail would only be checked when writing a new sstable
> to disk (fush/compact). Triggering the guardrail on sstable write would emit
> a log message and a diagnostic event, but it wouldn't reject the write.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
