[
https://issues.apache.org/jira/browse/HBASE-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511530#comment-15511530
]
Appy commented on HBASE-14734:
------------------------------
Patch isn't touching any of the failing tests. It touches HBaseTestingUtility,
but only adds a function without changing any existing logic. So the failures
are totally unrelated.
Still, ran the above timed out tests locally and they passed.
Committing.
{noformat}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.client.TestHCM
^[[DTests run: 24, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 310.58 sec
- in org.apache.hadoop.hbase.client.TestHCM
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running
org.apache.hadoop.hbase.client.TestIncrementFromClientSideWithCoprocessor
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.301 sec - in
org.apache.hadoop.hbase.client.TestIncrementFromClientSideWithCoprocessor
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 113.521 sec -
in org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.client.TestMultiRespectsLimits
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.173 sec - in
org.apache.hadoop.hbase.client.TestMultiRespectsLimits
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.client.TestReplicasClient
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 254.478 sec -
in org.apache.hadoop.hbase.client.TestReplicasClient
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClientWithRegionReplicas
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 94.408 sec - in
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClientWithRegionReplicas
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.client.TestSnapshotMetadata
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.885 sec - in
org.apache.hadoop.hbase.client.TestSnapshotMetadata
Results :
Tests run: 61, Failures: 0, Errors: 0, Skipped: 1
{noformat}
> BindException when setting up MiniKdc
> -------------------------------------
>
> Key: HBASE-14734
> URL: https://issues.apache.org/jira/browse/HBASE-14734
> Project: HBase
> Issue Type: Sub-task
> Components: flakey, test
> Reporter: stack
> Assignee: Appy
> Attachments: HBASE-14734.master.001.patch
>
>
> Root cause : Port for kdc service gets selected in the constructor, but we
> bind to it later in MiniKdc.start()-->MiniKdc.initKDCServer() -->
> KdcServer.start(). In meantime, some other service can capture the port which
> results in BindException. The solution here is to catch the exception and
> retry.
> From
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.2/330/jdk=latest1.7,label=Hadoop/testReport/junit/org.apache.hadoop.hbase.security.token/TestGenerateDelegationToken/org_apache_hadoop_hbase_security_token_TestGenerateDelegationToken/
> Error Message
> Address already in use
> Stacktrace
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at
> org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:198)
> at
> org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:51)
> at
> org.apache.mina.core.polling.AbstractPollingIoAcceptor.registerHandles(AbstractPollingIoAcceptor.java:547)
> at
> org.apache.mina.core.polling.AbstractPollingIoAcceptor.access$400(AbstractPollingIoAcceptor.java:68)
> at
> org.apache.mina.core.polling.AbstractPollingIoAcceptor$Acceptor.run(AbstractPollingIoAcceptor.java:422)
> at
> org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Can this utility be made to not fail if address taken? Try another?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
