[
https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915729#comment-16915729
]
Rajeshbabu Chintaguntla commented on RATIS-556:
-----------------------------------------------
bq.But, I thought that was the plan – to close the log when we lose a peer.
bq.Oh, I see where the confusion is, I think we agreed that if peer/s of the
quorum goes down and quorum size of a log is reduced to 2(or unsafe no. , could
be configurable), we should automatically close those logs and start the
archival process. so that we don't keep the unsafe quorum/logs lingering for
long.
Ok, I am making changes accordingly.
Thanks for the review.
> Detect node failures and close the log to prevent additional writes
> -------------------------------------------------------------------
>
> Key: RATIS-556
> URL: https://issues.apache.org/jira/browse/RATIS-556
> Project: Ratis
> Issue Type: Improvement
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Attachments: RATIS-556-wip.patch, RATIS-556_v1.patch
>
>
> Currently there is no way to detect the node failures at master log servers
> and add new nodes to the group serving the log. We need to analyze how Ozone
> is working in this case.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
