[
https://issues.apache.org/jira/browse/RATIS-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated RATIS-2273:
-------------------------------
Description:
RATIS-1298 discussed the possibility and designs of having a Ratis listener
which listens from non-leader (e.g. follower or another listeners). The idea is
that since Ratis listener will never be a voting-member, it is safe to just
replicate the Raft logs of any follower up to the commitIndex.
This can be useful in the case of HDDS-12307 for asynchronous replication from
non-leader node since it doesn't require the most up-to-date state.
was:
RATIS-1298 discussed the possibility and designs of having a Ratis listener
which listens from non-leader (e.g. follower or another listeners). The idea is
that since Ratis listener will never be a voting-member, it is safe to just
replicate the Raft logs of any follower up to the commitIndex.
This can be useful in the case of HDDS-12307 for asynchronous replication from
non-leader node since it doesn't require the most up-to-date data.
> Support Ratis listener sync from non-leader
> -------------------------------------------
>
> Key: RATIS-2273
> URL: https://issues.apache.org/jira/browse/RATIS-2273
> Project: Ratis
> Issue Type: Improvement
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> RATIS-1298 discussed the possibility and designs of having a Ratis listener
> which listens from non-leader (e.g. follower or another listeners). The idea
> is that since Ratis listener will never be a voting-member, it is safe to
> just replicate the Raft logs of any follower up to the commitIndex.
> This can be useful in the case of HDDS-12307 for asynchronous replication
> from non-leader node since it doesn't require the most up-to-date state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
