[
https://issues.apache.org/jira/browse/HDFS-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237178#comment-16237178
]
HalfLegend commented on HDFS-12694:
-----------------------------------
I find the cause, but still don't know why.
I stopped the firewall on Host3, and then restarted the hdfs on docker3.
Everything goes fine. So the problem is because of the firewall.
I established a VPN server on host3, using the firewall to forward requests. I
opened all the ports on host3.
This is the configuration of the firewall:
$ firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eno1
sources:
services: dhcpv6-client ssh ipsec
ports: 1-65534/tcp 500/udp 4500/udp 1-65534/udp
protocols:
masquerade: yes
forward-ports:
source-ports:
icmp-blocks:
rich rules:
Please confirm, which configuration affects the register of the data node.
> Wrong data node registered in docker
> ------------------------------------
>
> Key: HDFS-12694
> URL: https://issues.apache.org/jira/browse/HDFS-12694
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.8.0, 2.7.4, 2.8.1
> Environment: There hosted machines and each one have a docker.
> Hosted machines: host1, host2, host3
> dockers : docker1, docker2, docker3
> I installed HDFS in each docker. (version 2.8.1)
> Docker1 and Docker2 have name node.
> Docker1,2,3 all have data node.
> I have a weave network of 10.240.1.0/24
> Reporter: HalfLegend
> Priority: Major
>
> Somebody else installed another HDFS in hosted machine outside the dockers.
> But the data node in the hosted machine appears in the docker machine.
> | Node | Http Address | Capacity | Blocks | Block pool used | Version|
> | docker1:50010 (10.240.1.101:50010) | docker1:50075 | 931.06 GB |
> 8420 | 116.64 GB (12.53%) | 2.8.1 |
> | docker2:50010 (10.240.1.102:50010) | docker2:50075 | 916.77 GB | 8420 |
> 116.64 GB (12.72%) | 2.8.1 |
> | docker3:50010 (10.240.1.64:50010) | docker3:50075 | 916.77 GB | 0 | 28 KB
> (0%) | 2.8.1 |
> The IP address of docker3 should be 10..240.1.103, but it is 10.240.1.64 here
> which is the IP address of host3. They also have a data node running on host3.
> We can see in docker3, the used blocks is 0, no data is added here. The
> replication is 3.
> If I use fsck to check the files, many replication blocks are missing. I
> think it is because of the IP address.
> Further more, if I stop the data node in docker3, the heart beat will stop.
> This is correct.
> So it is a weird bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
