[
https://issues.apache.org/jira/browse/HDDS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686320#comment-16686320
]
Shashikant Banerjee commented on HDDS-834:
------------------------------------------
Thanks [~msingh] for reporting and working on this. The patch looks good to me.
I am +1 on the patch with some minor changes:
1) containerCommandCompletionMap renamed to applyTransactionCompletionMap in
ContainerStateMachine.
2) Adding some more comments while adding dummy entries in
applyTransactionCompletionMap.
I will take care of these while committing.
> Datanode goes OOM based because of segment size
> -----------------------------------------------
>
> Key: HDDS-834
> URL: https://issues.apache.org/jira/browse/HDDS-834
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.3.0
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Attachments: HDDS-834-ozone-0.3.001.patch, HDDS-834.001.patch
>
>
> Currently ratis segment size is set to 1GB. After RATIS-253, the entry size
> for a write Chunk is not counted towards the entry being written to Raft Log.
> This jira controls the segment size to 16KB which makes sure that the number
> of entries with WriteChunk is limited to 64. This means with 16MB chunk, the
> total data pending in the segment is 1GB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
