[
https://issues.apache.org/jira/browse/RATIS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884041#comment-16884041
]
Tsz Wo Nicholas Sze commented on RATIS-613:
-------------------------------------------
> ... It might be required by use cases of Ratis where applyTransaction call is
> slower?
Ratis should work as fast as it can. In this case, the slowness is in the
state machine so that it should be the place to enforce a limit to protect
itself.
Even if we do the limit in Ratis, ContainerStateMachine still won't work on the
stand alone case.
> 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, RATIS-613.002.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.14#76016)
