[
https://issues.apache.org/jira/browse/HBASE-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722735#comment-13722735
]
Nicolas Liochon commented on HBASE-9012:
----------------------------------------
Hi Stack :-)
Actually there is another scenario: another process / test took the port
between the time we killed and the time we try to take the port. I'm not sure
it's that scenario, because usually the OS is supposed to wait a little before
allocating the same port. But who knows? So we could fix this by checking that
we've been able to take the port, and if not, skip the next step? This could
work as well if the DN is still there, whatever the reason.
If you're ok with the approach I will write a patch.
> TestBlockReorder.testBlockLocationReorder fails
> -----------------------------------------------
>
> Key: HBASE-9012
> URL: https://issues.apache.org/jira/browse/HBASE-9012
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
> Fix For: 0.95.2
>
> Attachments: 9012.txt
>
>
> http://54.241.6.143/job/HBase-0.95/669/org.apache.hbase$hbase-server/testReport/junit/org.apache.hadoop.hbase.fs/TestBlockReorder/testBlockLocationReorder/
> java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
> at java.net.ServerSocket.bind(ServerSocket.java:328)
> at java.net.ServerSocket.<init>(ServerSocket.java:194)
> at java.net.ServerSocket.<init>(ServerSocket.java:106)
> at
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocationReorder(TestBlockReorder.java:182)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
