[
https://issues.apache.org/jira/browse/RATIS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825578#comment-16825578
]
Josh Elser commented on RATIS-533:
----------------------------------
{{Log.setByteLimit}} and {{Log.setElementLimit}} control the "size" of the
queue which holds edits that need to be persisted to the RAFT log. This queue
holds any I/O related operation: write data, create a new segment, etc. If we
have significant I/O backpressure, we may want to increase this queue to ride
over that backpressure. This would be good to understand in metrics.
> 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)
