[SOLR-1781] Replication index directories not always cleaned up

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: 4.0-BETA, 6.0
• Component/s: replication (java), SolrCloud

Environment

Windows Server 2003 R2, Java 6b18

• Assignee: Mark Miller
• Reporter: Terje Sten Bjerkseth
• Created: 19/Feb/10 15:13
• Updated: 09/May/16 18:46
• Resolved: 26/Jul/12 14:38

Description

We had the same problem as someone described in http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201001.mbox/[e-mail]%3e. A partial copy of that message:

We're using the new replication and it's working pretty well. There's
one detail I'd like to get some more information about.

As the replication works, it creates versions of the index in the data
directory. Originally we had index/, but now there are dated versions
such as index.20100127044500/, which are the replicated versions.

Each copy is sized in the vicinity of 65G. With our current hard drive
it's fine to have two around, but 3 gets a little dicey. Sometimes
we're finding that the replication doesn't always clean up after
itself. I would like to understand this better, or to not have this
happen. It could be a configuration issue.

Issue Links

• is related to: SOLR-3592 After reloading a SolrCore, some IndexWriter 'settings' changes will not take effect. Instead, you must restart Solr.