[
https://issues.apache.org/jira/browse/CASSANDRA-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403647#comment-15403647
]
Benjamin Lerer commented on CASSANDRA-12106:
--------------------------------------------
bq. Regarding keeping this cache b/w co-ordinator and replicas, we chose
replica since it is more efficient to keep it there since this list can grow
and we want to reduce the things in memory.
In my opinion, we should probably look at the pros and cons of each approach.
Implementing the functionnalty at the coordinator level will result in a much
smaller change. The logic will be easier to understand/maintain and there will
less chances to let a problem slip through.
I agree, that amount of memory used could be a problem at some point. How much
memory do you think you will need in the worst case scenario that you have seen
so far? Is it really unrealistic to have it at the coordinator level?
> 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)
