You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2021/06/09 08:39:00 UTC
[jira] [Commented] (IGNITE-13885) Investigate jraft implementation
for replication framework based on RAFT protocol.
[ https://issues.apache.org/jira/browse/IGNITE-13885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359868#comment-17359868 ]
Mirza Aliev commented on IGNITE-13885:
--------------------------------------
As far as jraft is isolated and there is an umbrella ticket with TODOs, I would say that we can merge it as is. LGTM
> Investigate jraft implementation for replication framework based on RAFT protocol.
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-13885
> URL: https://issues.apache.org/jira/browse/IGNITE-13885
> Project: Ignite
> Issue Type: Task
> Reporter: Alexey Scherbakov
> Assignee: Alexey Scherbakov
> Priority: Major
> Labels: iep-61, ignite-3
> Fix For: 3.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> jraft: https://www.sofastack.tech/en/projects/sofa-jraft/overview
> Investigation points:
> # Ease of custom RPC implementation.
> # Threading model fit.
> # Liveness guaranties [1]
> # State machine overload safety.
> [1] [https://decentralizedthoughts.github.io/2020-12-12-raft-liveness-full-omission/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)