On 3/17/2017 11:14 AM, Imad Qureshi wrote:
> I understand that but unfortunately that's not an option right now. We
> already have 16 TB of index in HDFS.
>
> So let me rephrase this question. How important is data locality for SOLR. Is
> performance impacted if SOLR data is on a remote node?
W
Imad Qureshi wrote:
> I understand that but unfortunately that's not an option right now.
> We already have 16 TB of index in HDFS.
>
> So let me rephrase this question. How important is data locality for
> SOLR. Is performance impacted if SOLR data is on a remote node?
The short answer is yes,
Hi Mike
I understand that but unfortunately that's not an option right now. We already
have 16 TB of index in HDFS.
So let me rephrase this question. How important is data locality for SOLR. Is
performance impacted if SOLR data is on a remote node?
Thanks
Imad
> On Mar 17, 2017, at 12:02 PM,
I've only ever used the HDFS support with Cloudera's build, but my
experience turned me off to use HDFS. I'd much rather use the native file
system over HDFS.
On Tue, Mar 14, 2017 at 10:19 AM, Muhammad Imad Qureshi <
imadgr...@yahoo.com.invalid> wrote:
> We have a 30 node Hadoop cluster and each
We have a 30 node Hadoop cluster and each data node has a SOLR instance also
running. Data is stored in HDFS. We are adding 10 nodes to the cluster. After
adding nodes, we'll run HDFS balancer and also create SOLR replicas on new
nodes. This will affect data locality. does this impact how solr w
