Re: UN-SUBSCRIBE ME PLEASE - 2ND REQUEST...
you are sending email to wrong address. Send email to solr-user-unsubscr...@lucene.apache.org. ThanksImad On Friday, June 1, 2018, 11:11:06 AM CDT, wrote: THIS IS MY 2ND REQUEST - PLEASE UNSUBSCRIBE ME
SOLR 4.10.3 - Replication for DR strategy
I know this is a very old version and we are working to upgrade this to SOLR 5.5. In the meantime, We also know how to do the replication by copying indexed data from the file system. Currently on prod a particular shard (shard1/replica1) has a directory called “/core_node_97”. When we move data from prod to DR, it copies data to same directory in DR (core_node97). How do we ensure that shard is also pointing to exact same directory? In this setup, shard1/replica1 has data in core_node97 on prod but on DR the directory is “core_node1” which is not right. I would want shard1/replica1 on DR side to point to core_node97. I have tried exporting clusterjstate.son from zookeeper after modifying ip addresses to point to the ip addresses from DR (but that didn't help). ThanksImad
Number of shards - Best practice
Hi I was recently told that ideally the number of shards in a SOLR cluster should be equal to a power of 2. If this is indeed a best practice, then what is the rationale behind this recommendation? ThanksImad
SOLR Data Locality
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 works (I mean performance) if the data is on a remote node? ThanksImad
Benefits of Data Locality in SOLR
We have a 30 node Hadoop cluster and each data node has a SOLR instance also running. We are adding 10 nodes. After adding nodes, we'll run HDFS balancer. This will affect data locality. does this impact how solr works (I mean performance)? ThanksImad
