Are you sure you have your namenode URL set correctly? Usually the namenode
URL points at port 8020, whereas the RPC port is 8022.

To answer the original question, CDH 5 ships with a patched Solr 4.6. If
that's the version you want to run, you might as well use theirs. I have a
testing cluster with 4.8.1 pointing at a CDH 5 HDFS, and a production
cluster with 4.9 as well.

Michael Della Bitta

Applications Developer

o: +1 646 532 3062

appinions inc.

“The Science of Influence Marketing”

18 East 41st Street

New York, NY 10017

t: @appinions <https://twitter.com/Appinions> | g+:
plus.google.com/appinions
<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts>
w: appinions.com <http://www.appinions.com/>


On Fri, Aug 29, 2014 at 12:59 PM, nagyMarcelo <nagymarce...@gmail.com>
wrote:

> I´m with the same problem.
> This is what is throw.
>
> RuntimeException: Problem creating directory:
> hdfs://
> 10.58.10.147:8022/usr/solr/FavorecidoHdfs/core_node1/BY9/lws-main/data/solr/cores/favorecidohdfs_6/data/FavorecidoHdfs_shard1_replica1
>         at
> org.apache.solr.store.hdfs.HdfsDirectory.<init>(HdfsDirectory.java:89)
>         at
>
> org.apache.solr.core.HdfsDirectoryFactory.create(HdfsDirectoryFactory.java:148)
>         at
>
> org.apache.solr.core.CachingDirectoryFactory.get(CachingDirectoryFactory.java:350)
>         at org.apache.solr.core.SolrCore.getNewIndexDir(SolrCore.java:267)
>         at org.apache.solr.core.SolrCore.initIndex(SolrCore.java:477)
>         at org.apache.solr.core.SolrCore.<init>(SolrCore.java:772)
>         ... 10 more
> Caused by: java.io.IOException: Failed on local exception:
> com.google.protobuf.InvalidProtocolBufferException: Message missing
> required
> fields: callId, status; Host Details : local host is:
> "scixd0021cld.itau/10.58.10.147"; destination host is:
> "scixd0021cld.itau":8022;
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-and-HDFS-tp4155470p4155872.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

Reply via email to