[
https://issues.apache.org/jira/browse/RATIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852433#comment-16852433
]
Vladimir Rodionov commented on RATIS-520:
-----------------------------------------
{quote}
Let me know what you think about the segment size for the metadata quorum.
{quote}
I do not see any value in that option, [~elserj].
> [Configuration] Unify configuration across client and server code
> -----------------------------------------------------------------
>
> Key: RATIS-520
> URL: https://issues.apache.org/jira/browse/RATIS-520
> Project: Ratis
> Issue Type: Sub-task
> Affects Versions: 0.4.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Major
> Fix For: 0.4.0
>
> Attachments: RATIS-520-v1.patch, RATIS-520-v2.patch,
> RATIS-520-v3.patch, RATIS-520-v4.patch
>
>
> Configuration of implementation specific details inside of Ratis itself need
> to be created as they presently are static. The ability to configure them on
> the fly for administration of the system is a must.
> Work breakdown:
> RATIS-477 has some implementation of LogStateMachine configuration.
> Need a method to configure the MetadataStateMachine and LogStateMachine(s)
> with LogService-level configuration. For example:
> Command-line arguments to specify configuration key=values
> Configuration file which can be specified
> Something else… (with justification why chosen)
> Potentially, can the system be dynamically reconfigured.
> Method of configuring the system must be clearly documented
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
