[
https://issues.apache.org/jira/browse/RATIS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626297#comment-16626297
]
Josh Elser commented on RATIS-279:
----------------------------------
Well summarized, [~sergey.soldatov]. Totally agree on all of your points above.
Sorry I missed this when you sent it out the first time :)
Some other considerations...
* We should have a well-encapsulated "package' for the metadataStateMachine.
It would be great to have something so simple as instantiating an object and
calling {{start()}} (or similar) on it. This keeps integration into HBase
simple, but also would be easy for us to lift the "service" into a Java process
that we run on its own (e.g. maybe for doing testing).
* 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. Sergey mentioned that this is something
that will ultimately have to be built into Ratis and subsequently exposed in
the LogService?
Good stuff.
> 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)
