[
https://issues.apache.org/jira/browse/RATIS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659879#comment-16659879
]
Sergey Soldatov commented on RATIS-334:
---------------------------------------
[~vrodionov] well, my point is that this class is ambiguous because:
1. It uses raft client. And the stream class that provides reader/writer uses
that raft client, so we can say that this client is the one based on Log quorum.
2. Log quorum is created by the meta service during .createLog() call, so this
method should not be the part of LogService class.
3. createLog() in LogService is a remote call that returns LogStream. But the
only thing that we create remotely is the raft group which will be used by raft
client. But as I already mentioned, LogStream actually takes raft client from
the LogService.
> 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
> Reporter: Josh Elser
> Assignee: Sergey Soldatov
> Priority: Major
> 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)
