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

Yonik Seeley edited comment on SOLR-9310 at 8/22/16 3:01 PM:
-------------------------------------------------------------

bq. What is the need for the cache?

Multiple replicas syncing against each other (or all replicas syncing against a 
new leader...)  I *think* it's part of the protocol to elect a new leader 
(because when one leader goes down, we don't know which replicas may have 
received the last update(s) and which replicas did not...)  In such a scenario, 
there is no active indexing because no new leader yet.
Some people run with large numbers of replicas (10 or 20), and hence the 
difference could well be large.



was (Author: ysee...@gmail.com):
bq. What is the need for the cache?

Multiple replicas syncing against each other... I *think* it's part of the 
protocol to elect a new leader (because when one leader goes down, we don't 
know which replicas may have received the last update(s) and which replicas did 
not...)  In such a scenario, there is no active indexing because no new leader 
yet.
Some people run with large numbers of replicas (10 or 20), and hence the 
difference could well be large.


> PeerSync fails on a node restart due to IndexFingerPrint mismatch
> -----------------------------------------------------------------
>
>                 Key: SOLR-9310
>                 URL: https://issues.apache.org/jira/browse/SOLR-9310
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Pushkar Raste
>            Assignee: Noble Paul
>             Fix For: trunk, 6.3
>
>         Attachments: PeerSync_3Node_Setup.jpg, PeerSync_Experiment.patch, 
> SOLR-9310.patch, SOLR-9310.patch, SOLR-9310.patch, SOLR-9310.patch, 
> SOLR-9310.patch, SOLR-9310_3ReplicaTest.patch, SOLR-9310_final.patch
>
>
> I found that Peer Sync fails if a node restarts and documents were indexed 
> while node was down. IndexFingerPrint check fails after recovering node 
> applies updates. 
> This happens only when node restarts and not if node just misses updates due 
> reason other than it being down.
> Please check attached patch for the test.



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

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

Reply via email to