Bumping this.
I'm seeing the error mentioned earlier in the thread - "Unable to download
completely. Downloaded 0!=" often in my logs. I'm
dealing with a situation where maxDoc count is growing at a faster rate
than numDocs and is now almost twice as large. I'm not optimizing but
rather relying o
Folks, would really appreciate if somebody can help/throw some light on
below issue . This issue is blocking our upgrade, we are doing a 3.x to
4.x upgrade and indexing around 100g of data.
Any help would be highly appreciated.
Thanks,
Anand
On 1/3/2014 11:46 AM, anand chandak wrote:
Thank
Thanks Shalin.
I am facing one issue while replicating, as my replication (very large
index 100g)is happening, I am also doing the indexing and I believe the
segment_N file is changing because of new commits. So would the
replication fail if the the filename is different from what it found
w
Replications won't run concurrently. They are scheduled at a fixed
rate and if a particular pull takes longer than the time period then
subsequent executions are delayed until the running one finishes.
On Tue, Dec 31, 2013 at 4:46 PM, anand chandak wrote:
> Quick question about solr replication :
