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

Optimize HistoryAffinityAssignment heap usage.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8
    • None
    • None

    Description

      With large topology and large amount of caches/partitions many server discovery events may quickly produce large affinity history, eating gigabytes of heap.

      Solution: implement some kind of a compression for affinity cache map.

      On example, affinity history could be stored as delta to some previous version.

       

      Attachments

        Issue Links

          Activity

            People

              kbolyandra Konstantin Bolyandra
              ascherbakov Alexey Scherbakov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m