You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2023/04/10 05:33:00 UTC
[jira] [Updated] (IGNITE-18273) Remove JRaft classes from ignite-raft module API
[ https://issues.apache.org/jira/browse/IGNITE-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko updated IGNITE-18273:
-------------------------------------
Description:
{{JRaft}} is a 3-rd party Raft implementation and is considered an implementation detail of the {{ignite-raft}} module. We would have a cleaner design if we would encapsulate this library with our own API. Some work regarding this issue has been done in IGNITE-18265, but one problem remains: in-memory Raft and the {{RaftGroupOptions}} class that is used to configure it. We need to encapsulate this class or introduce a different way for configuring in-memory Raft.
After this is done, we should migrate the remaining code to use the {{RaftManager}} interface.
We also need to move *org.apache.ignite.internal.raft.RaftNodeDisruptorConfiguration* to *org.apache.ignite.internal.raft.server.RaftGroupOptions*.
was:
{{JRaft}} is a 3-rd party Raft implementation and is considered an implementation detail of the {{ignite-raft}} module. We would have a cleaner design if we would encapsulate this library with our own API. Some work regarding this issue has been done in IGNITE-18265, but one problem remains: in-memory Raft and the {{RaftGroupOptions}} class that is used to configure it. We need to encapsulate this class or introduce a different way for configuring in-memory Raft.
After this is done, we should migrate the remaining code to use the {{RaftManager}} interface.
> Remove JRaft classes from ignite-raft module API
> ------------------------------------------------
>
> Key: IGNITE-18273
> URL: https://issues.apache.org/jira/browse/IGNITE-18273
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> {{JRaft}} is a 3-rd party Raft implementation and is considered an implementation detail of the {{ignite-raft}} module. We would have a cleaner design if we would encapsulate this library with our own API. Some work regarding this issue has been done in IGNITE-18265, but one problem remains: in-memory Raft and the {{RaftGroupOptions}} class that is used to configure it. We need to encapsulate this class or introduce a different way for configuring in-memory Raft.
> After this is done, we should migrate the remaining code to use the {{RaftManager}} interface.
> We also need to move *org.apache.ignite.internal.raft.RaftNodeDisruptorConfiguration* to *org.apache.ignite.internal.raft.server.RaftGroupOptions*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)