[
https://issues.apache.org/jira/browse/CASSANDRA-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136968#comment-15136968
]
T Jake Luciani commented on CASSANDRA-11082:
--------------------------------------------
It's true, we should be checking isWritable() though I don't imagine we should
condone/support many slow clients as a good use case for cassandra (it should
be behind a firewall with local connections).
The simplest place to put it is in our flushing logic. But what should we do
drop the data on the floor? I imagine that would break the protocol so might be
better to simply close the connection? wdyt [~slebresne]
> netty's level hadn't prevent OOM when receiver handle slow.
> -----------------------------------------------------------
>
> Key: CASSANDRA-11082
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11082
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: fujian
>
> as we know, netty will OOM when received client is slow.
> due to if receiver can't handle response fast so that cassandra server can't
> flush data. it will cause channeloutbuffer with big size.
> we see the cassandra had configure write high/low water level, but I can't
> found any code to judge iswritable. so it will have possible OOM
> why cassandra hadn't handle this case?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
