[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=14018273#comment-14018273 ] Hudson commented on HBASE-6139: --- SUCCESS: Integrated in HBase-TRUNK #5174 (See [https://builds.apache.org/job/HBase-TRUNK/5174/]) HBASE-6139 Add troubleshooting section for CentOS 6.2 page allocation failure issue (Misty Stanley-Jones) (stack: rev f24e68426c9d17389258c0f501ad1f1f025971cf) * src/main/docbkx/troubleshooting.xml > 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: Misty Stanley-Jones > Fix For: 0.99.0 > > Attachments: HBASE-6139.patch > > > 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 was sent by Atlassian JIRA (v6.2#6252)
[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=14016273#comment-14016273
]
Hadoop QA commented on HBASE-6139:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12648069/HBASE-6139.patch
against trunk revision .
ATTACHMENT ID: 12648069
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ This issue is known to affect CentOS 6.2 and possibly
CentOS 6.5. It may also affect
+
xlink:href="http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s3-proc-sys-vm.html";
/>.
+ [user@host]# echo >
/proc/sys/vm/min_free_kbytes
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9674//console
This message is automatically generated.
> 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: Misty Stanley-Jones
> Attachments: HBASE-6139.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
[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=14015523#comment-14015523 ] Lars Francke commented on HBASE-6139: - I'm fine with not adding this but I've seen this on a CentOS 6.5 machine recently (I think, not sure). > 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: Misty Stanley-Jones > > 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 was sent by Atlassian JIRA (v6.2#6252)
[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
