Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 28 Jan 2016 00:51:39 +0000 (UTC)
From: "fujian (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12934649.1453942241000.231425.1453942299889@Atlassian.JIRA>
In-Reply-To: <JIRA.12934649.1453942241000@Atlassian.JIRA>
References: <JIRA.12934649.1453942241000@Atlassian.JIRA>
 <JIRA.12934649.1453942241830@arcas>
Subject: [jira] [Created] (CASSANDRA-11082) netty's level hadn't prevent OOM
 when receiver handle slow.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

fujian created CASSANDRA-11082:
----------------------------------

             Summary: 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
            Priority: Critical


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)