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

Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2019/12/06 05:56:39 UTC

[GitHub] [hadoop-ozone] mukul1987 opened a new pull request #320: HDDS-2683. Ratis MaxBuffer should be the same size as the segment size.

mukul1987 opened a new pull request #320: HDDS-2683. Ratis MaxBuffer should be the same size as the segment size.
URL: https://github.com/apache/hadoop-ozone/pull/320
 
 
   ## What changes were proposed in this pull request?
   
   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 jira sets the max buffer size same as segment size.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-2683
   
   ## How was this patch tested?
   Ran MiniOzoneChaosCluster with the new config to ensure data read/write are working fine.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org