lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anand chandak <>
Subject Re: Very long running replication.
Date Fri, 03 Jan 2014 06:16:20 GMT
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 
when fetching the filename list.

Basically, I am seeing this exception :

[explicit-fetchindex-cmd] ERROR 
org.apache.solr.handler.ReplicationHandler- SnapPull failed 
:org.apache.solr.common.SolrException: Unable to download _av3.fdt 
completely    . Downloaded 0!=497037
   2     at 
   3     at 
   4     at 
   5     at 
   6     at 
   7     at 

And I am trying to find the root cause of this issue. Any help ?



On 1/2/2014 5:32 PM, Shalin Shekhar Mangar wrote:
> 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 : What happens if there's a
>> replication running for very large index that runs more than the interval
>> for 2 replication ? would the automatic runs of replication interfere with
>> the current running one or it would not even spawn next iteration of
>> replication ? Can somebody throw some light ?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message