[jira] [Commented] (HBASE-6450) HBase startup should be with MALLOC_MAX_ARENA set
[ https://issues.apache.org/jira/browse/HBASE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428736#comment-13428736 ] Hudson commented on HBASE-6450: --- Integrated in HBase-0.94-security-on-Hadoop-23 #6 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/6/]) HBASE-6450 HBase startup should be with MALLOC_MAX_ARENA set (Revision 1365583) Result = FAILURE stack : Files : * /hbase/branches/0.94/bin/hbase-config.sh HBase startup should be with MALLOC_MAX_ARENA set - Key: HBASE-6450 URL: https://issues.apache.org/jira/browse/HBASE-6450 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.92.2, 0.94.2 Attachments: 6450.patch I think we should do the same as what HADOOP-7154 has done in terms of starting up daemons with MALLOC_MAX_ARENA set. I recently noticed that there were RS crashes on RHEL6 due to memory (could be avoided by setting MALLOC_MAX_ARENA). -- 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
[jira] [Commented] (HBASE-6450) HBase startup should be with MALLOC_MAX_ARENA set
[ https://issues.apache.org/jira/browse/HBASE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428762#comment-13428762 ] Hudson commented on HBASE-6450: --- Integrated in HBase-0.94-security #47 (See [https://builds.apache.org/job/HBase-0.94-security/47/]) HBASE-6450 HBase startup should be with MALLOC_MAX_ARENA set (Revision 1365583) Result = SUCCESS stack : Files : * /hbase/branches/0.94/bin/hbase-config.sh HBase startup should be with MALLOC_MAX_ARENA set - Key: HBASE-6450 URL: https://issues.apache.org/jira/browse/HBASE-6450 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.92.2, 0.94.2 Attachments: 6450.patch I think we should do the same as what HADOOP-7154 has done in terms of starting up daemons with MALLOC_MAX_ARENA set. I recently noticed that there were RS crashes on RHEL6 due to memory (could be avoided by setting MALLOC_MAX_ARENA). -- 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
[jira] [Commented] (HBASE-6450) HBase startup should be with MALLOC_MAX_ARENA set
[ https://issues.apache.org/jira/browse/HBASE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13422380#comment-13422380 ] Hudson commented on HBASE-6450: --- Integrated in HBase-0.92 #481 (See [https://builds.apache.org/job/HBase-0.92/481/]) HBASE-6450 HBase startup should be with MALLOC_MAX_ARENA set (Revision 1365582) Result = SUCCESS stack : Files : * /hbase/branches/0.92/bin/hbase-config.sh HBase startup should be with MALLOC_MAX_ARENA set - Key: HBASE-6450 URL: https://issues.apache.org/jira/browse/HBASE-6450 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.92.2, 0.94.2 Attachments: 6450.patch I think we should do the same as what HADOOP-7154 has done in terms of starting up daemons with MALLOC_MAX_ARENA set. I recently noticed that there were RS crashes on RHEL6 due to memory (could be avoided by setting MALLOC_MAX_ARENA). -- 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
[jira] [Commented] (HBASE-6450) HBase startup should be with MALLOC_MAX_ARENA set
[ https://issues.apache.org/jira/browse/HBASE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13422761#comment-13422761 ] Hudson commented on HBASE-6450: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #110 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/110/]) HBASE-6450 HBase startup should be with MALLOC_MAX_ARENA set (Revision 1365584) Result = FAILURE stack : Files : * /hbase/trunk/bin/hbase-config.sh HBase startup should be with MALLOC_MAX_ARENA set - Key: HBASE-6450 URL: https://issues.apache.org/jira/browse/HBASE-6450 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.92.2, 0.94.2 Attachments: 6450.patch I think we should do the same as what HADOOP-7154 has done in terms of starting up daemons with MALLOC_MAX_ARENA set. I recently noticed that there were RS crashes on RHEL6 due to memory (could be avoided by setting MALLOC_MAX_ARENA). -- 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
[jira] [Commented] (HBASE-6450) HBase startup should be with MALLOC_MAX_ARENA set
[ https://issues.apache.org/jira/browse/HBASE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421819#comment-13421819 ] Hadoop QA commented on HBASE-6450: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12537751/6450.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 5 javac compiler warnings (more than the trunk's current 4 warnings). -1 findbugs. The patch appears to introduce 14 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2433//console This message is automatically generated. HBase startup should be with MALLOC_MAX_ARENA set - Key: HBASE-6450 URL: https://issues.apache.org/jira/browse/HBASE-6450 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.92.2 Attachments: 6450.patch I think we should do the same as what HADOOP-7154 has done in terms of starting up daemons with MALLOC_MAX_ARENA set. I recently noticed that there were RS crashes on RHEL6 due to memory (could be avoided by setting MALLOC_MAX_ARENA). -- 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
