hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6727) [89-fb] allow HBaseServers's callqueue to be better configurable to avoid OOMs
Date Sun, 21 Oct 2012 00:02:12 GMT

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

stack commented on HBASE-6727:

Created HBASE-7023 to forward-port this facility that is nicer than what we have in trunk.
> [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: Adela Maznikar
>             Fix For: 0.89-fb
>         Attachments: 6727.txt
> The callQueue size (where requests get queued up if all handlers are busy) is a LinkedBlockingQueue
of size 100 * number_of_handlers. So, with say 300 handler threads, the call queue can have
upto 30k entries queued up. If the requests are large enough, this can result in OOM or severe
GC pauses.
> Ideally, we should allow this param to be separately configurable independent of the
numberof handlers; perhaps an even better approach would be to specify a memory size based
limit, instead of a number of entries based limit.
> [I have not looked at the trunk version for this issue. So it may or may not be relevant

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

View raw message