[
https://issues.apache.org/jira/browse/RATIS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185454#comment-17185454
]
Tsz-wo Sze commented on RATIS-624:
----------------------------------
I suggest to have the following subtasks.
# add pause() and resume() to RaftServerImpl so that they can be used
internally.
#- If we want to expose them later on, we can add them to RaftClient. The new
APIs, say groupPause and groupResume, should be similar to groupAdd and
groupRemove.
# change server detect itself for lagging behind by a configurable threshold.
# change server to ask for installing snapshot if it detects itself lagging
behind. This task need a more detailed design.
#- Who should take a snapshot?
#- It probably need some kind of policy -- in some application, taking a
snapshot is very efficient but some may not.
Any thoughts?
> RaftServer should support pause/ unpause in its LifeCycle state
> ---------------------------------------------------------------
>
> Key: RATIS-624
> URL: https://issues.apache.org/jira/browse/RATIS-624
> Project: Ratis
> Issue Type: Task
> Reporter: Hanisha Koneru
> Assignee: Rui Wang
> Priority: Major
> Labels: ozone
> Fix For: 1.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This Jira aims to add support to RaftServer to support pause and unpause to
> its state. When paused, the RaftServer should not accept any incoming append
> log entries.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
