[
https://issues.apache.org/jira/browse/BEAM-6047?focusedWorklogId=165719&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-165719
]
ASF GitHub Bot logged work on BEAM-6047:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Nov/18 00:49
Start Date: 14/Nov/18 00:49
Worklog Time Spent: 10m
Work Description: chamikaramj closed pull request #7025: [BEAM-6047] Try
to fix HDFS DNS issues
URL: https://github.com/apache/beam/pull/7025
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/sdks/python/apache_beam/io/hdfs_integration_test/docker-compose.yml
b/sdks/python/apache_beam/io/hdfs_integration_test/docker-compose.yml
index 60f7194de0b..73e567c0a05 100644
--- a/sdks/python/apache_beam/io/hdfs_integration_test/docker-compose.yml
+++ b/sdks/python/apache_beam/io/hdfs_integration_test/docker-compose.yml
@@ -24,6 +24,7 @@ services:
hostname: namenode
environment:
- CLUSTER_NAME=test
+ -
HDFS_CONF_dfs_namenode_datanode_registration_ip___hostname___check=false
networks:
- test_net
diff --git
a/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
b/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
index 1eeb43b3722..a2bf5f09254 100755
--- a/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
+++ b/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
@@ -34,6 +34,13 @@ cp -r ${ROOT_DIR}/model ${CONTEXT_DIR}/
# Use a unique name to allow concurrent runs on the same machine.
PROJECT_NAME=$(echo hdfs_IT-${BUILD_TAG:-non-jenkins})
+if [ -z "${BUILD_TAG:-}" ]; then
+ COLOR_OPT=""
+else
+ COLOR_OPT="--no-ansi"
+fi
+COMPOSE_OPT="-p ${PROJECT_NAME} ${COLOR_OPT}"
+
cd ${CONTEXT_DIR}
# Clean up leftover unused networks from previous runs. BEAM-4051
# This might mess with leftover containers that still reference pruned
networks,
@@ -42,10 +49,10 @@ cd ${CONTEXT_DIR}
docker network prune --force
function finally {
- time docker-compose -p ${PROJECT_NAME} down
+ time docker-compose ${COMPOSE_OPT} down
}
trap finally EXIT
-time docker-compose -p ${PROJECT_NAME} build
-time docker-compose -p ${PROJECT_NAME} up --exit-code-from test \
+time docker-compose ${COMPOSE_OPT} build
+time docker-compose ${COMPOSE_OPT} up --exit-code-from test \
--abort-on-container-exit --force-recreate
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 165719)
Time Spent: 2h 20m (was: 2h 10m)
> hdfsIntegrationTest is failing due to DisallowedDatanodeException
> -----------------------------------------------------------------
>
> Key: BEAM-6047
> URL: https://issues.apache.org/jira/browse/BEAM-6047
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core, test-failures
> Reporter: Chamikara Jayalath
> Assignee: Udi Meiri
> Priority: Critical
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> beam_PostCommit_Python_Verify is perma red due to this.
>
> [https://scans.gradle.com/s/pqg3ent77c2pu/console-log?task=:beam-sdks-python:hdfsIntegrationTest#L1653]
>
> [36mnamenode_1_d5b2d221b2e2 |[0m
> org.apache.hadoop.hdfs.server.protocol.DisallowedDatanodeException: Datanode
> denied communication with
> namenode because hostname cannot be resolved (ip=172.18.0.3,
> hostname=172.18.0.3): DatanodeRegistration(0.0.0.0:50010,
> datanodeUuid=717d9e8f-ff6b-449c-bc94-6deb57455f93, infoPort=50075,
> infoSecurePort=0, ipcPort=50020,
> storageInfo=lv=-57;cid=CID-ef5ccec9-8245-45cc-9cc1-b103684e8ce1;nsid=1522131886;c=1542034438259)
>
>
> [33mdatanode_1_3ee1bc415f49 |[0m 18/11/10 18:03:06 ERROR datanode.DataNode:
> Initialization failed for Block pool BP-15607
> 62326-172.18.0.2-1541872973618 (Datanode Uuid
> 367ac165-40b3-437f-97dc-567cb8d15da5) service to namenode/172.18.0.2:8020
> Datanode denied communication with namenode because hostname cannot be
> resolved (ip=172.18.0.3, hostname=172.18.0.3):
> DatanodeRegistration(0.0.0.0:50010,
> datanodeUuid=367ac165-40b3-437f-97dc-567cb8d15da5, infoPort=50075,
> infoSecurePort=0, ipcPort=50020,
> storageInfo=lv=-57;cid=CID-d00d4259-9d80-4952-85d1-a0012d91842d;nsid=1271723208;c=1541872973618)
>
> Udi, any idea ?
>
> cc: [~swegner] [~altay]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
