You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Francke (JIRA)" <ji...@apache.org> on 2012/05/31 18:14:23 UTC

[jira] [Commented] (HBASE-6139) Add troubleshooting section for CentOS 6.2 page allocation failure issue

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

Lars Francke commented on HBASE-6139:
-------------------------------------

We googled basically and found multiple people with similar problems on CentOS/RedHat 6.2 so we tried what they tried and the suggestion was to double/quadruple {{min_free_kbytes}} until it works. It was set at 90112 initially but this is automatically calculated at boot depending on available memory so it'll vary from system to system. This is on a machine with 64 GB memory.

We also found a [bug|https://bugzilla.redhat.com/show_bug.cgi?id=770545] in RedHat's bugzilla. We haven't tried setting {{vm.zone_reclaim_mode}} to {{1}} yet but will probably try that tomorrow.

Doublink {{min_free_kbytes}} we still saw those issues but quadrupling it helped.
                
> Add troubleshooting section for CentOS 6.2 page allocation failure issue
> ------------------------------------------------------------------------
>
>                 Key: HBASE-6139
>                 URL: https://issues.apache.org/jira/browse/HBASE-6139
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>
> Tim Robertson reports:
> bq. HBase CentOS version 6.2 reports kernel: java: page allocation failure. order:4, mode:0x20. Any ideas anyone?
> Then:
> bq. echo 360448 > /proc/sys/vm/min_free_kbytes appears to stop page allocation failure using HBase on CentOS 6.2
> If this is the proper fix for this condition, we should document it.
> @Tim, how did you arrive at 360448?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira