fix for "java.io.IOException: No FileSystem for scheme: hdfs" error#1721
fix for "java.io.IOException: No FileSystem for scheme: hdfs" error#1721fjy merged 1 commit intoapache:masterfrom
Conversation
|
tested it manually, looks like it fixes the issue. |
bde9f7c to
1b286b4
Compare
|
👍 |
1b286b4 to
b989a70
Compare
|
@fjy rebased to latest master |
fix for "java.io.IOException: No FileSystem for scheme: hdfs" error
|
I merged the changes in #1721 (https://github.com/druid-io/druid/pull/1721/files) into the druid release tagged "druid-0.8.1" and it seems that this issue still occurs. See my previous comments on #1022. |
|
I have tried to repro it with apache hadoop 2.6.0 and druid-0.8.1 and it worked fine for me. However, I am not sure what is wrong here. |
|
It might be worth mentioning here that when I set the following in "druid-0.8.1/config/_common/common.runtime.properties": It resulted in the following exception in my logs: Even though the following dependencies existed: ls -al druid-0.8.1/extensions-repo/org/apache/hadoop/hadoop-hdfs/2.7.1/
8260573 Oct 14 17:17 hadoop-hdfs-2.7.1.jar
23707 Oct 14 17:13 hadoop-hdfs-2.7.1.pom |
|
Does it work if you do "org.apache.hadoop:hadoop-hdfs:2.7.1" rather than "org.apache.hadoop.hadoop-hdfs:2.7.1"? (colon between the group and artifact) |
|
Nice catch @gianm. One thing I did notice, was that other than the one exception log shown above, I don't see any further exceptions related to this, even when I had the invalid hadoop-hdfs value. For instance, I changed my current value to: And I have yet to see any exceptions related to this "invalid-client", even after successful Druid segments have been created. |
|
Issue seems to be resolved in the latest Druid 0.8.2 release: http://static.druid.io/artifacts/releases/druid-0.8.2-bin.tar.gz |
aka workaround for https://issues.apache.org/jira/browse/HDFS-8750
replaces #1022 , #1716
Fixes #1714