You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2017/12/08 03:28:02 UTC

[jira] [Commented] (SOLR-11702) Redesign current LIR implementation

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

Mike Drob commented on SOLR-11702:
----------------------------------

Ooooh, good approach. This is similar in concept to how RAFT works, I think.

One thing that is unclear from design doc (haven't looked at code yet) is who updated the ZK terms when replica joins recovery. Is that the result of the leader acknowledging the PrepRecoveryCmd?

> Redesign current LIR implementation
> -----------------------------------
>
>                 Key: SOLR-11702
>                 URL: https://issues.apache.org/jira/browse/SOLR-11702
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Cao Manh Dat
>            Assignee: Cao Manh Dat
>         Attachments: SOLR-11702.patch
>
>
> I recently looked into some problem related to racing between LIR and Recovering. I would like to propose a totally new approach to solve SOLR-5495 problem because fixing current implementation by a bandage will lead us to other problems (we can not prove the correctness of the implementation).
> Feel free to give comments/thoughts about this new scheme.
> https://docs.google.com/document/d/1dM2GKMULsS45ZMuvtztVnM2m3fdUeRYNCyJorIIisEo/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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