[
https://issues.apache.org/jira/browse/SOLR-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416330#comment-13416330
]
Mark Miller commented on SOLR-1781:
-----------------------------------
bq. after some time has passed?
This was tempting for a moment - but it feels dirty.
You could just say, hey, do it on the next core restart - but that may not come
for a long time.
You'd really like to be able to tell when all the indexreaders on the old dir
are done, but that is very difficult it turns out. The only easy way to do it
is to reload the core.
If you replicate configuration files, you have to reload the core anyway. I'd
say it's probably the way to go. It should not be that much more expensive than
reloading a searcher in the larger scheme of replication.
> Replication index directories not always cleaned up
> ---------------------------------------------------
>
> Key: SOLR-1781
> URL: https://issues.apache.org/jira/browse/SOLR-1781
> Project: Solr
> Issue Type: Bug
> Components: replication (java), SolrCloud
> Affects Versions: 1.4
> Environment: Windows Server 2003 R2, Java 6b18
> Reporter: Terje Sten Bjerkseth
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments:
> 0001-Replication-does-not-always-clean-up-old-directories.patch
>
>
> We had the same problem as someone described in
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201001.mbox/%3c222a518d-ddf5-4fc8-a02a-74d4f232b...@snooth.com%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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
