You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/06 05:57:00 UTC
[jira] [Updated] (HDDS-2683) Ratis MaxBuffer should be the same
size as the segment size
[ https://issues.apache.org/jira/browse/HDDS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-2683:
---------------------------------
Labels: pull-request-available (was: )
> Ratis MaxBuffer should be the same size as the segment size
> -----------------------------------------------------------
>
> Key: HDDS-2683
> URL: https://issues.apache.org/jira/browse/HDDS-2683
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Labels: pull-request-available
>
> As noticed with RATIS-767, the write buffer is allocated with 32MB size whereas the raft log segment is 1MB. The rest of the buffer will not be used and the memory is wasted allocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org