lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yury Kats <yuryk...@yahoo.com>
Subject Re: Replication: abortfetch is broken if replication was started by fetchindex?
Date Tue, 27 Sep 2011 14:58:37 GMT
Related question/issue: what about core close hook? Does it need to abort
replication if a core is being deleted while it's replicating (started by fetchhindex)?


On 9/23/2011 7:39 AM, Shalin Shekhar Mangar wrote:
> You are right Yury. It is a bug. The fix is to use tempSnapPuller.abortPull always because
tempSnapPuller is always the snap puller doing the actual work. Have you opened an issue yet?
> 
> 2011/9/23 Yury Kats <yurykats@yahoo.com <mailto:yurykats@yahoo.com>>
> 
>     If I start replication by issuing a "fetchindex" command with a "masterUrl"
>     parameter, it seems to me (by looking at the trunk code) that "abortfetch" command
>     would not do anything. It appears to be aborting only when replication is
>     configured with hardcoded master/slave cores.
> 
>     Is this intentional? An oversight? Am I missing something in the code and
>     abortfetch does work in all cases?
> 
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <mailto:dev-unsubscribe@lucene.apache.org>
>     For additional commands, e-mail: dev-help@lucene.apache.org <mailto:dev-help@lucene.apache.org>
> 
> 
> 
> 
> -- 
> Regards,
> Shalin Shekhar Mangar.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message