On 9/1/2014 10:31 AM, Mauricio Ferreyra wrote: > I'm using Solr 4.3.1 with a master/slave configuration. > > Configuration: > > Master: > * <lst name="master">* > * <str name="replicateAfter">commit</str>* > * <str name="replicateAfter">startup</str>* > * <str name="confFiles">schema.xml,stopwords.txt</str>* > * </lst>* > > > Slave: > * <lst name="slave">* > * <str name="masterUrl">http://10.xx.xx.xx:9081/solr > <http://10.xx.xx.xx:9081/solr></str>* > * <str name="pollInterval">00:00:60</str>* > * </lst>* > > The replication sometimes fails with the exception > > *Error closing old IndexWriter. > core=collection1:java.lang.IllegalArgumentException: Unknown directory: > NRTCachingDirectory...* > *ReplicationHandler SnapPull failed :org.apache.solr.common.SolrException: > Index fetch failed :* > > This is happening with any index size.
We would need the entire stacktrace from that error message to make any real determination, but without that, I offer this: If it's happening with a tiny index (kilobytes or only a few megabytes), then I would suspect a bug in Solr. 4.3.1 is ancient history now -- Solr's development and release schedule is very aggressive. There have been ten new versions in the 14 months since 4.3.1 was announced, and the 4.10 release is imminent. There have been a number of replication bugs fixed in those releases. If "any index size" means that some of them are in the range of several gigabytes, then it may simply be a configuration problem. The commitReserveDuration parameter may need increasing beyond its default of ten seconds. Large updates after optimizing or a major automatic merge can take many minutes to transfer, and if that parameter is set too low, the old index can disappear before it can finish replicating. Thanks, Shawn
