[
https://issues.apache.org/jira/browse/RATIS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825579#comment-16825579
]
Josh Elser commented on RATIS-533:
----------------------------------
{{Snapshot.setAutoTriggerEnabled}} we definitely cannot set this to true. In
fact, I think we never want to have a snapshot occur ever, as this would result
in log segments being removed from disk. We're using the Raft log as a source
of truth – we cannot "roll up" and just get the same state from a snapshot of
our state machine.
> 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
>
> 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)
