[
https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885286#comment-16885286
]
Josh Elser commented on RATIS-556:
----------------------------------
I remember chit-chatting with [~an...@apache.org] about this. I think the idea
was that we could get some listener callback in the metadata quorum and force
that log into a "CLOSED" state, so that no more updates can be accepted by it.
However, if we force a CLOSED state via sending it a transaction which can't be
applied, maybe we have a bigger problem :)
> Detect node failures and add other workers to group serving the log and
> replicate the data of the log
> -----------------------------------------------------------------------------------------------------
>
> 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
>
> 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
(v7.6.14#76016)
