Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Hadoop 3 client #3

Open
sverhoeven opened this issue Nov 14, 2018 · 2 comments
Open

Use Hadoop 3 client #3

sverhoeven opened this issue Nov 14, 2018 · 2 comments

Comments

@sverhoeven
Copy link
Member

The Hadoop dependencies have some conflicts with Xenon and downstream applications. The Hadoop deps should be shaded so they do not conflict anymore.

The Hadoop 3 client java libraries are shaded already. If we switch to Hadoop 3 client libraries than this repo jars do not need to be shaded anymore.

@sverhoeven
Copy link
Member Author

Started work in https://github.com/NLeSC/xenon-adaptors-hadoop/tree/shaded-hadoop3 branch.

The existing tests against Hadoop 2 Docker container are still successful.

@sverhoeven
Copy link
Member Author

Trying to run test suite against Hadoop 3 Docker container is failing.

The hdfs name server is returning internal adress (127.0.0.1) of datanode which is not accessible from the unit test.
Error is:

13:02:37.113 [Thread-5] DEBUG org.apache.hadoop.hdfs.DataStreamer - pipeline = [DatanodeInfoWithStorage[127.0.0.1:9866,DS-88b8c019-ea28-4976-9728-82f670be37d3,DISK]], blk_1073741827_1003
13:02:37.114 [Thread-5] DEBUG org.apache.hadoop.hdfs.DataStreamer - Connecting to datanode 127.0.0.1:9866
13:02:37.115 [Thread-5] INFO  org.apache.hadoop.hdfs.DataStreamer - Exception in createBlockOutputStream blk_1073741827_1003
java.net.ConnectException: Connection refused

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant