[
https://issues.apache.org/jira/browse/CASSANDRA-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387642#comment-15387642
]
Jason Brown commented on CASSANDRA-12106:
-----------------------------------------
bq. it is not Cassandra's job to protect against malicious clients
True enough, but it would be great if we could prevent an entire cluster from
falling over under due to (some degree of) adverse conditions.
bq. bit too hand-wavy to my taste
We absolutely have these problems, in production, at our scale. It is not an
everyday occurrence, but neither is it entirely rare that a 'bad' partition
gets a cluster into a bad state (not exclusively the due to {{IndexInfo}}
GC-pressure, either). Thus, I think the desire to add additional resilience to
the database is a reasonable idea.
I worked with [~geoffxy] on some of the initial ideas for this patch, and
perhaps the implementation ended up a bit large, yet I would argue thorough.
That being said, I can work with Geoff on modifying/simplifying his patch to
perhaps something like [~slebresne]'s suggestion assuming it is a) workable and
b) meets the goals for this ticket and our production needs.
> 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)
