SolrCore load failure can leave newly created index locked
----------------------------------------------------------
Key: SOLR-2274
URL: https://issues.apache.org/jira/browse/SOLR-2274
Project: Solr
Issue Type: Bug
Reporter: Hoss Man
As noted by lance...
http://search.lucidimagination.com/search/document/d164b1b804dce166/default_file_locking_on_trunk
{noformat}
Date: Sun, 14 Nov 2010 14:09:30 -0800
From: Lance Norskog
To: solr-user
Subject: Re: Default file locking on trunk
...
When there is no existing data/index/ directory, Solr creates a new
index/ directory at the beginning of loading the core, locks it, but
does not flush out an empty index. Here's the problem: when the core
fails while being loaded (in this case because the core configuration
was bogus) it left the index/ directory locked. It did not flush out
the new empty index (just the segment* files).
So, if a core has no index, and fails during loading, it should either
write out an empty index as it intended to, or remove the half-built
data/index/ directory. Or just not make the empty index until loading
completes?
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
