[
https://issues.apache.org/jira/browse/RATIS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825546#comment-16825546
]
Josh Elser commented on RATIS-533:
----------------------------------
{{Log.setSegmentSizeMax}} defaults to 8MB which is the RAFT log segment we're
currently writing to. When a new segment is created, we'll initialize
{{Log.preallocatedSize}} of those bytes in the file, defaulting to 4MB. As we
append data, we'll write up to {{Log.setWriteBufferSize}} to disk at a time.
>From prior art, I know that we'll want to increase the segment size to prevent
>lots of segments from being created for a single log as well as preallocate
>the entire segment so that we don't pay the penalty multiple times (if we
>create the segment, we're likely to write to it later when latency actually
>matters). Increasing the size of the direct bytebuffer we use to write data to
>disk will also help amortize I/O costs.
> 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)
