You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org> on 2019/08/01 15:43:00 UTC

[jira] [Commented] (RATIS-556) Detect node failures and close the log to prevent additional writes

    [ https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898151#comment-16898151 ] 

Rajeshbabu Chintaguntla commented on RATIS-556:
-----------------------------------------------

Uploaded WIP patch. Currently, when a node goes down we cannot know which log to close because there is no indication the logs serve by the peer. So in the patch passing the peer(optional) while creating the log so that meta servers maintain the logs serve by the peer. So when a node goes down we can close the logs served by the peer which suites exactly in HBase case.

> 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
>
>
> 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)