From dd95ef77c09697056ee5508320ae4453017a07b6 Mon Sep 17 00:00:00 2001 From: Himanshu Gupta Date: Sat, 18 Jul 2015 16:18:12 -0500 Subject: [PATCH] recommend druid-hdfs-storage and hadoop dependencies to be in the classpath instead of added as an extension --- docs/content/ingestion/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/ingestion/faq.md b/docs/content/ingestion/faq.md index e832eadc980..3c1b5e1726b 100644 --- a/docs/content/ingestion/faq.md +++ b/docs/content/ingestion/faq.md @@ -40,7 +40,7 @@ Other common reasons that hand-off fails are as follows: ## How do I get HDFS to work? -Make sure to include the `druid-hdfs-storage` module as one of your extensions and set `druid.storage.type=hdfs`. You may also need to include hadoop configs on the classpath. +Make sure to include the `druid-hdfs-storage` and all the hadoop configuration, dependencies (that can be obtained by running command `hadoop classpath` on a machine where hadoop has been setup) in the classpath. And, provide necessary HDFS settings as described in [Deep Storage](../dependencies/deep-storage.html) . ## I don't see my Druid segments on my historical nodes You can check the coordinator console located at `:`. Make sure that your segments have actually loaded on [historical nodes](../design/historical.html). If your segments are not present, check the coordinator logs for messages about capacity of replication errors. One reason that segments are not downloaded is because historical nodes have maxSizes that are too small, making them incapable of downloading more data. You can change that with (for example):