lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-4709) dir lock error if reopening cores to fast?
Date Mon, 30 Dec 2013 00:53:51 GMT


ASF subversion and git services commented on SOLR-4709:

Commit 1554119 from [] in branch 'dev/trunk'
[ ]

SOLR-4709: Move CHANGES to 4.6.1

> dir lock error if reopening cores to fast?
> ------------------------------------------
>                 Key: SOLR-4709
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Mark Miller
>             Fix For: 5.0, 4.7, 4.6.1
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message