cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11082) netty's level hadn't prevent OOM when receiver handle slow.
Date Mon, 08 Feb 2016 10:59:39 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-11082:
-----------------------------------------
    Priority: Major  (was: Critical)

> 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)

Mime
View raw message