[jira] [Updated] (RATIS-410) Raft log entry with stateMachineData may cause OOM

["Shashikant Banerjee (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shashikant Banerjee updated RATIS-410:
--------------------------------------
    Summary: Raft log entry with stateMachineData may cause OOM  (was: entry with stateMachineData may cause OOM)

> Raft log entry with stateMachineData may cause OOM
> --------------------------------------------------
>
>                 Key: RATIS-410
>                 URL: https://issues.apache.org/jira/browse/RATIS-410
>             Project: Ratis
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 0.3.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: RATIS-410.001.patch, RATIS-410.002.patch, RATIS-410.003.patch
>
>
> With Ozone, each of raft log segments are of 1GB in size. Also each of the writeChunk request will have 16MB worth of payload. So this can result in multiple writeChunk requests to be part of one log segment.
> Because the caching policy in ratis works on eviction of log segments, these results in segments holding onto memory which is part of stateMachine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)