[
https://issues.apache.org/jira/browse/SOLR-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533511#comment-13533511
]
Yonik Seeley edited comment on SOLR-4203 at 12/16/12 9:12 PM:
--------------------------------------------------------------
Seems like another issue is that it could introduce a race...
starting the update log could start recovery, which may or may not finish
before the update log is closed.
edit: actually init() doesn't kick off recovery.
But the fact remains, UpdateLog was not meant to be closed and re-inited (there
is other state that probably doesn't get cleared, etc).
was (Author: [email protected]):
Seems like another issue is that it could introduce a race...
starting the update log could start recovery, which may or may not finish
before the update log is closed.
> An ephemeral directory implementation should cause the transaction log to be
> ignored on startup.
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-4203
> URL: https://issues.apache.org/jira/browse/SOLR-4203
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-4203.patch
>
>
> If you are using something like ram dir, you can restart a node and if no
> updates have come in, it will think its up to date but be empty - we should
> clear the update log in these cases on startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
