There might be a JIRA issue out there about replication not cleaning up on all fails - e.g. on startup or something - kind of rings a bell…if so, it will be addressed eventually.
Otherwise, you might have two for a bit just due to multiple searchers being around at once for a while or something - but it should not be something that lasts a long time. - Mark On Nov 20, 2013, at 11:50 AM, Daniel Collins <danwcoll...@gmail.com> wrote: > In our experience (with SolrCloud), if you trigger a full replication (e.g. > new replica), you get the "timestamp" directory, it never renames back to > just "index". Since index.properties gives you the name of the real > directory, we had never considered that a problem/bug. Why bother with the > rename afterwards, it just seems unnecessary? > > So to answer your questions: > > 1) Not in normal circumstances, but if replication crashes or stops, it > might leave it hanging. > 2) No, as long as there is an index.properties file. > > Not official answers, but that's our experience. > > > On 20 November 2013 15:55, michael.boom <my_sky...@yahoo.com> wrote: > >> I encountered this problem often when i restarted a solr instance before >> replication was finished more than once. >> I would then have multiple timestamped directories and the index directory. >> However, the index.properties points to the active index directory. >> >> The moment when the replication succeeded the temp dir is renamed "index" >> and the index.properties is gone. >> >> On the situation when the index is missing, not sure about that. Maybe this >> happens when the replica is too old and an old-school replication is done. >> >> >> >> ----- >> Thanks, >> Michael >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Multiple-data-index-YYYYMMDD-dirs-bug-tp4102163p4102168.html >> Sent from the Solr - User mailing list archive at Nabble.com. >>
