[
https://issues.apache.org/jira/browse/RATIS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626491#comment-16626491
]
Sergey Soldatov commented on RATIS-279:
---------------------------------------
bq. Ratis group membership. Will nodes available to participate send a message
via the RaftClient to the metadata service to report? We'll also need to be
able to detect when a node drops out.
That's the biggest question how to track that some of the nodes drop out. For
existing quorums (existing Logs) losing of the quorum members can be done by
the statemachine, so the leader of the quorum may report to the meta data
service. But if we have N nodes that were registered as available, but
eventually went dead and we need to know about that. So we want some kind of
heartbeats messages. Just had a conversation about that with Nicholas and he
said that ratis group MAY have its own statemachine different from the one we
specified in RaftServer builder. So we may create a group that would include
all workers (and would automatically be adjusted if a new worker started), so
we will use Ratis internal heartbeats to track live/dead servers.
> Create administrative API for a log stream
> ------------------------------------------
>
> Key: RATIS-279
> URL: https://issues.apache.org/jira/browse/RATIS-279
> Project: Ratis
> Issue Type: Sub-task
> Components: LogService
> Reporter: Josh Elser
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Attachments: RATIS-279_WIP.patch, RATIS-279_v2.patch,
> RATIS-279_v3.patch
>
>
> We need to do basic things like:
> * List all log streams
> * Delete a log stream
> * Truncate a log stream
> This may overlap with functionality that actually should live in HBase.
> Making that distinction is part of the tasks of this issue.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
