[jira] [Resolved] (SOLR-4709) dir lock error if reopening cores to fast?

["Mark Miller (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller resolved SOLR-4709.
-------------------------------

    Resolution: Fixed

> dir lock error if reopening cores to fast?
> ------------------------------------------
>
>                 Key: SOLR-4709
>                 URL: https://issues.apache.org/jira/browse/SOLR-4709
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Mark Miller
>             Fix For: 5.0, 4.7
>
>
> While testing my patch for SOLR-4629, i noticed a really random error that i traced back to the core reload (do to config file replication) failed because the directory was locked.
> From what i can tell, the lock checking code in the SolrCore constructor isn't even suppose to be used in the reload situation where there is a "prev" core, except that in SolrCore.reload there is this check...
> {noformat}
>     if (!getNewIndexDir().equals(getIndexDir())) {
>       // the directory is changing, don't pass on state
>       prev = null;
>     }
> {noformat}
> ..i'm not really sure i understand this logic, or what exactly the source of the problem is, or if the lock checking code should just be changed to work a differnet way completley, but it seemed worthy of tracking in it's own jira.
> log details to follow



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org