[
https://issues.apache.org/jira/browse/RATIS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved RATIS-334.
------------------------------
Resolution: Fixed
Fix Version/s: 0.3.0
Thanks for the patch, [~sergey.soldatov]. This is a nice starting point. It's
cool to see this coming together.
Please spin out follow-on Jira issues to do the cleanup mentioned in the
code-review here.
> Implement server membership for LogService Metadata Service
> -----------------------------------------------------------
>
> Key: RATIS-334
> URL: https://issues.apache.org/jira/browse/RATIS-334
> Project: Ratis
> Issue Type: Sub-task
> Components: LogService
> Reporter: Josh Elser
> Assignee: Sergey Soldatov
> Priority: Major
> Fix For: 0.3.0
>
> Attachments: RATIS-334-v1.patch, RATIS-334-v3.patch,
> RATIS-334-wip.patch
>
>
> Half of the Metadata Service for managing LogStreams.
> RATIS-279 is handling the "DDL" operations, and Rajesh suggested that we spin
> out management of the servers which are available to back these LogStreams in
> a second task. This is it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
