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 <[email protected] <mailto:[email protected]>> > > 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: [email protected] > <mailto:[email protected]> > For additional commands, e-mail: [email protected] > <mailto:[email protected]> > > > > > -- > Regards, > Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
