Uploaded image for project: 'Ratis'
  1. Ratis
  2. RATIS-613

StateMachineUpdater should limit the number of apply transaction calls

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Bug
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ljain Lokesh Jain
            ljain Lokesh Jain
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment