Hoss Man created SOLR-11988:

             Summary: FullSolrCloudDistribCmdsTest failures due to SolrCore 
initializating incorrectly thinking index directory already exists?
                 Key: SOLR-11988
                 URL: https://issues.apache.org/jira/browse/SOLR-11988
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Hoss Man

There's been quite a few jenkins failures from FullSolrCloudDistribCmdsTest 
that all seem to follow a similar pattern:
 * Failure manifests as "Could not find collection:collection2"
 * Failing seeds _frequently_ reproduce, but aren't guaranteed to
 * Root cause can be traced back to the collection creation failing because one 
of more replica cores failed due to the brand new (Solr)IndexWriter expects to 
find an existing segments file
 ** SolrCore should have already created an (empty) index in 
 ** The fact that the {{SolrIndexWrite}} throws this exception in it's 
constructor suggests that the earlier call to {{SolrCore.initIndex(...)}} is 
not functioning reliably
 ** Based on some experimenting i've done, it seems like the underlying problem 
is that in {{SolrCore.initIndex(...)}} the DirectoryFactory can "lie" about 
wether a directory already exists.

More details to follow in comments.

This message was sent by Atlassian JIRA

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

Reply via email to