hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kannan Muthukkaruppan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6727) [89-fb] allow HBaseServers's callqueue to be better configurable to avoid OOMs
Date Thu, 06 Sep 2012 23:41:08 GMT

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

Kannan Muthukkaruppan updated HBASE-6727:
-----------------------------------------

    Assignee: Michal Gregorczyk  (was: Kannan Muthukkaruppan)
    
> [89-fb] allow HBaseServers's callqueue to be better configurable to avoid OOMs
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-6727
>                 URL: https://issues.apache.org/jira/browse/HBASE-6727
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Michal Gregorczyk
>
> The callQueue size (where requests get queued up if all handlers are busy) is a LinkedBlockingQueue
of size 100*# of handlers. So, with say 300 handler threads, the call queue can have upto
30k entries queued up. If the requests are large enough-- then this can result in OOM or severe
GC pauses.
> Ideally, we should allow this param to be separately configurable independent of the
# of handlers; and better still be able to specify a memory size based limit, instead of a
# of entries based limit.
> [I have not looked at the trunk version for this issue. So it may or may not be relevant
there.]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message