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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RATIS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882231#comment-16882231 ] 

Hadoop QA commented on RATIS-613:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 13s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red} RATIS-613 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/ratis:date2019-07-10 |
| JIRA Issue | RATIS-613 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12974230/RATIS-613.001.patch |
| Console output | https://builds.apache.org/job/PreCommit-RATIS-Build/893/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> 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)