There really shouldn't be anything cloudera specific here. We write to hbase 
and not directly to native hdfs. But basically instead of adding those 
properties to cloudera manager configs, you need to add them to the 
hdfs-site.xml or core-site.xml ( don't remember which one off the top of my 
head, leaning towards hdfs-site) files your storm topologies are referencing. 

Then your topologies should pick up those configs. 

Sent from my iPhone

> On Jun 22, 2015, at 7:34 PM, P. Taylor Goetz <[email protected]> wrote:
> 
> There might be others here that are using Storm with CDH, but since Cloudera 
> Manager is closed source/proprietary, you may well be better off asking the 
> question on a Cloudera forum for specific details.
> 
> That being said, the community here is likely willing to help, but you’ll 
> need to get past the Cloudera-specific pieces and down to the open source 
> parts. If you know the HDFS URL for the cluster, you should be able to 
> connect.
> 
> What version of Storm are you using? When you say “trying to write to hadoop” 
> do you mean HDFS, or something else? Are you using the storm-hdfs component 
> that ships with Apache Storm?
> 
> The more details you can provide the better the community will be able to 
> help you.
> 
> -Taylor
> 
>> On Jun 22, 2015, at 8:06 PM, Ajay Chander <[email protected]> wrote:
>> 
>> Hi Everyone,
>> 
>> I am trying to write the data into hadoop from my storm topology. For this 
>> communication to happen through hostnames, I have enabled couple of 
>> properties namely "dfs.client.use.datanode.hostname"=true and  
>> "dfs.datanode.use.datanode.hostname" = true in my cloudera manager. Now how 
>> do I make my storm aware of those two properties. When my storm topology is 
>> running by default it takes those properties as false. Now how do I override 
>> those properties ("dfs.client.use.datanode.hostname"=true and  
>> "dfs.datanode.use.datanode.hostname" = true) which are specific to my hadoop 
>> in my hdfsbolt. ??
>> 
>> Any help is highly appreciated.
>> 
>> Thank you,
>> Ajay
> 

Reply via email to