[
https://issues.apache.org/jira/browse/CASSANDRA-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386505#comment-15386505
]
sankalp kohli commented on CASSANDRA-12106:
-------------------------------------------
I dont think you are negative here :)
There are cases in which there are large partitions due to spammers, etc which
we need to blacklist for the time being till it is fixed. We cannot have one
partition take down the cluster while it is fixed. Uptime is important and
hence this feature. The reason this patch is big is because we want to make the
foundation so that we can automatically blacklist bad partitions in the future.
Regarding occurrence of this, this could be very common based on the app using
Cassandra. Also with CASSANDRA-9754, there is still a limit you want CQL
partitions to grow.
Regarding the unit test, Geoff is working on it and will also include a Dtest
for this.
> Add ability to blacklist a CQL partition so all requests are ignored
> --------------------------------------------------------------------
>
> Key: CASSANDRA-12106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12106
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Geoffrey Yu
> Assignee: Geoffrey Yu
> Priority: Minor
> Fix For: 4.x
>
> Attachments: 12106-trunk.txt
>
>
> Sometimes reads/writes to a given partition may cause problems due to the
> data present. It would be useful to have a manual way to blacklist such
> partitions so all read and write requests to them are rejected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
