Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 1 Jul 2016 17:23:11 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12986121.1467366834000.6748.1467393791168@Atlassian.JIRA>
In-Reply-To: <JIRA.12986121.1467366834000@Atlassian.JIRA>
References: <JIRA.12986121.1467366834000@Atlassian.JIRA> <JIRA.12986121.1467366834036@arcas>
Subject: [jira] [Commented] (HBASE-16165) Decrease RpcServer.callQueueSize
 before writeResponse causes OOM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 01 Jul 2016 17:23:13 -0000


    [ https://issues.apache.org/jira/browse/HBASE-16165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359323#comment-15359323 ] 

Enis Soztutar commented on HBASE-16165:
---------------------------------------

Did you see this happening, or theoretical by reading code? Just asking.

> Decrease RpcServer.callQueueSize before writeResponse causes OOM
> ----------------------------------------------------------------
>
>                 Key: HBASE-16165
>                 URL: https://issues.apache.org/jira/browse/HBASE-16165
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>
> In RpcServer, we use {{callQueueSizeInBytes}} to avoid queuing too many calls which causes OOM. But in {{CallRunner.run}}, we decrease it before send the response back. And even after calling {{sendResponseIfReady}}, the call object could stay in our heap for a long time if we can not write out the response(That's why we need a Responder thread...). This makes it possible that the actual size of all call object in heap is larger than {{maxQueueSizeInBytes}} and causes OOM.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)