[
https://issues.apache.org/jira/browse/HBASE-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871338#comment-13871338
]
Hadoop QA commented on HBASE-10123:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12622962/hbase-10123.v2.patch
against trunk revision .
ATTACHMENT ID: 12622962
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{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:
+ <% master.getConfiguration().getInt("hbase.master.info.port", 16010)
%>/master-status" target="_blank">
+ <% master.getConfiguration().getInt("hbase.master.info.port", 16010)
%>/master-status" target="_blank">
+ ... the '1' means use ports 16001 & 16011, and this
backup master's logfile will be at
<filename>logs/hbase-${USER}-1-master-${HOSTNAME}.log</filename>.
+ <para>RegionServers starts a web-interface on port 16030 by
default. (Prior to 0.98 this was port 60030)
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.TestAcidGuarantees.testMixedAtomicity(TestAcidGuarantees.java:351)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8424//console
This message is automatically generated.
> Change default ports; move them out of linux ephemeral port range
> -----------------------------------------------------------------
>
> Key: HBASE-10123
> URL: https://issues.apache.org/jira/browse/HBASE-10123
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.1.1
> Reporter: stack
> Assignee: Jonathan Hsieh
> Priority: Critical
> Fix For: 0.98.0
>
> Attachments: hbase-10123.patch, hbase-10123.v2.patch
>
>
> Our defaults clash w/ the range linux assigns itself for creating come-and-go
> ephemeral ports; likely in our history we've clashed w/ a random, short-lived
> process. While easy to change the defaults, we should just ship w/ defaults
> that make sense. We could host ourselves up into the 7 or 8k range.
> See http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
