Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-3905

Optimize RendezvousAffinityFunction

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

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Duplicate
    • 1.6
    • 2.1
    • cache, general
    • None

    Description

      Currently RendezvousAffinityFunction.assignPartition generates a lot of garbage if called very often, on example in case of rebalancing a lot of caches.

      This causes excessive pressure on GC, which is not always fast enough to clear memory, producing long GC pauses leading to node segmentation.

      We should cache calculation of nodeHashBytes in node attribute or resort to more efficient node hash calculation.

      Attachments

        Issue Links

        duplicates

        Bug - A problem which impairs or prevents the functions of the product. IGNITE-3018 Cache affinity calculation is slow with large nodes number

        • Major - Major loss of function.
        • Resolved

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

          People

            Unassigned Unassigned
            ascherbakov Alexey Scherbakov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment