[
https://issues.apache.org/jira/browse/RATIS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622715#comment-16622715
]
Rajeshbabu Chintaguntla commented on RATIS-279:
-----------------------------------------------
[~sergey.soldatov]
bq. This API means that LogService has some kind of metadata storage that
allows us to manage a set of logs. Where and how it's going to be implemented.
These all we can do in LogStateMachine with the configurable directory to store
all the logs and the meta data information of the log files can be get from the
LogStateMachine right? We need to add all the request types added in the patch
to LogStateMachine to collect all the meta data.
bq. having a medata storage would mean that there is some kind of master server
which manages all this stuff and it would require some additional
configuration, recovery/discovery mechanism
For discovery mechanism we can create another task I think.
> 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
>
>
> 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)
