You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/05/03 18:10:00 UTC

[jira] [Resolved] (RATIS-533) Set important server config options for logservice

     [ https://issues.apache.org/jira/browse/RATIS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved RATIS-533.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.0

Fixed in [https://github.com/apache/incubator-ratis/pull/18]

> Set important server config options for logservice
> --------------------------------------------------
>
>                 Key: RATIS-533
>                 URL: https://issues.apache.org/jira/browse/RATIS-533
>             Project: Ratis
>          Issue Type: Improvement
>          Components: LogService
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: 0.4.0
>
>
> Mukul was kind enough to link to [https://github.com/apache/hadoop/blob/d31c86892e0ceec5d642f76fc9123fac4fd80db8/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/XceiverServerRatis.java] in Ozone which lists a bunch of RatisServer configuration keys that Ozone sets.
> We should go through this list and set the ones that make sense for the LogService too. For example, initial testing with a longer leader election timeout helps significantly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)