You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2019/05/29 22:18:00 UTC

[jira] [Comment Edited] (RATIS-520) [Configuration] Unify configuration across client and server code

    [ https://issues.apache.org/jira/browse/RATIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851352#comment-16851352 ] 

Vladimir Rodionov edited comment on RATIS-520 at 5/29/19 10:17 PM:
-------------------------------------------------------------------

Patch v2. cc: [~elserj]


was (Author: vrodionov):
Patch v2. cc: [~jelser]

> [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
>
>
> 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)