lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9512) CloudSolrClient's cluster state cache can break direct updates to leaders
Date Mon, 19 Sep 2016 10:33:20 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503044#comment-15503044
] 

Noble Paul commented on SOLR-9512:
----------------------------------

bq.Looking at HttpSolrCall it appears that it's only used in /select requests,

It must be a serious bug. Without proper invalidation,  the caching is useless

> CloudSolrClient's cluster state cache can break direct updates to leaders
> -------------------------------------------------------------------------
>
>                 Key: SOLR-9512
>                 URL: https://issues.apache.org/jira/browse/SOLR-9512
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Alan Woodward
>         Attachments: SOLR-9512.patch
>
>
> This is the root cause of SOLR-9305 and (at least some of) SOLR-9390.  The process goes
something like this:
> Documents are added to the cluster via a CloudSolrClient, with directUpdatesToLeadersOnly
set to true.  CSC caches its view of the DocCollection.  The leader then goes down, and is
reassigned.  Next time documents are added, CSC checks its cache again, and gets the old view
of the DocCollection.  It then tries to send the update directly to the old, now down, leader,
and we get ConnectionRefused.



--
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