lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "phil watson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-8641) Core Deleted After Failed Index Fetch When Replication Disabled
Date Thu, 04 Feb 2016 13:29:39 GMT
phil watson created SOLR-8641:
---------------------------------

             Summary: Core Deleted After Failed Index Fetch When Replication Disabled
                 Key: SOLR-8641
                 URL: https://issues.apache.org/jira/browse/SOLR-8641
             Project: Solr
          Issue Type: Bug
          Components: replication (java)
    Affects Versions: 5.1
         Environment: Windows Server 2008 R2
            Reporter: phil watson


I am getting occasional Index Fetch Failures (due to server overloading I suspect). This is
appearing in my log file as

Master at: http://MOTOSOLR01:9000/solr/ShowcaseData is not available. Index fetch failed.
Exception: Server refused connection at: http://MOTOSOLR01:9000/solr/ShowcaseData

At the point of the failure the master version of the core has replication disabled (but still
contains data) and it appears that on the next replication cycle that the slave version of
the core is being emptied. Once replication is enabled everything works as expected.

Having looked at the source code I suspect that lines 311-327 in indexfetcher.java are at
fault. What I think is happening is that the failed IndexFetch is setting forcereplication
to true, and this cause a forced delete of the core before reloading the core (which then
doesn't happen as replication is disabled)






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message