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

Allocated RAM is always 0 for non-persistent regions of persistent cluster

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.9
    • Fix Version/s: 2.11
    • Component/s: persistence
    • Labels:
      None
    • Release Note:
      Fixed Allocated RAM metric for in-memory data regions on persistent node
    • Ignite Flags:
      Release Notes Required

      Description

      org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#wrapMetricsMemoryProvider

      The logic in overridden nextRegion() method for the DirectMemoryProvider in the case above does not work for non-persistent data regions, as an example, region with persistenceEnabled=false, initSize = maxSize = 2G has only a single chunk that writes into memMetrics.updateCheckpointBufferSize(chunkSize) instead of memMetrics.updateOffHeapSize(chunkSize).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ilyak Ilya Kasnacheev
                Reporter:
                ilyak Ilya Kasnacheev
                Reviewer:
                Anton Kurbanov
              • Votes:
                0 Vote for this issue
                Watchers:
                5 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 - 0.5h
                  0.5h