[
https://issues.apache.org/jira/browse/HBASE-25139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209510#comment-17209510
]
Duo Zhang commented on HBASE-25139:
-----------------------------------
The problem is that, the infra team configured something like this in /etc/hosts
{noformat}
44.238.162.242 jenkins-hbase7.apache.org jenkins-hbase7
{noformat}
This is OK for normal machines in IDC, but for EC2 instance on AWS, the
44.238.162.242 is an EIP, which is something like a NAT gateway, as on the
machine you can not see 44.238.162.242 when running ifconfig(only 172.x.x.x).
But in hbase code, we will use hostname to bind the rpc server, then it will
resolve jenkins-hbase7 to 44.238.162.242 which causes the problem
{noformat}
org.apache.hbase.thirdparty.io.netty.channel.unix.Errors$NativeIoException:
bind(..) failed: Cannot assign requested address
{noformat}
[~gmcdonald] from the infra team helped to change the /etc/hosts file to
something like
{noformat}
172.31.14.131 jenkins-hbase4
44.239.213.191 jenkins-hbase4.apache.org
{noformat}
which solved the problem.
> The new hbase jenkins node has something wrong when running UTs
> ---------------------------------------------------------------
>
> Key: HBASE-25139
> URL: https://issues.apache.org/jira/browse/HBASE-25139
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
