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

Posted to issues@ratis.apache.org by "Lokesh Jain (JIRA)" <ji...@apache.org> on 2019/07/10 15:53:00 UTC

[jira] [Updated] (RATIS-613) StateMachineUpdater should limit the number of apply transaction calls

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

Lokesh Jain updated RATIS-613:
------------------------------
    Attachment: RATIS-613.001.patch

> StateMachineUpdater should limit the number of apply transaction calls
> ----------------------------------------------------------------------
>
>                 Key: RATIS-613
>                 URL: https://issues.apache.org/jira/browse/RATIS-613
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Major
>         Attachments: RATIS-613.001.patch
>
>
> Currently StateMachineUpdater applies all the transactions until the committed index. In cases where there is a huge difference between applied and committed index, all these transactions would be pending in the state machine and can take a lot of heap space. Such a scenario was seen in the Ozone cluster where a large amount of heap was taken by unapplied transactions leading to frequent GC pauses.



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