Details

    • Type: Sub-task
    • Status: Done
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: BLAZEGRAPH_RELEASE_1_5_2
    • Component/s: None
    • Labels:
      None

      Description

      This is a feature request to support a limit on the amount of native memory that can be used by the analytic query mode.

      1. Modify MemoryManager to accept the "blocks" boolean as a constructor argument. When blocks:=false, the MemoryManager will throw an out of memory exception. This will break queries that attempt to consume to much native memory.
      2. Add property (with a System property to override the default) that specifies the maximum amount of native memory that may be consumed by a query. When 0L there will be no limit.
      3. When the maximum amount of native memory is NOT 0L, then specify blocks:=false to AbstractRunningQuery.getMemoryManager(). This will cause queries that consume too much native memory to break with a MemoryManagerOutOfMemory exception.
      • See AbstractRunningQuery.getMemoryManager()
      • See PipelineOp.MAX_MEMORY (this is not quite the same concept since it specified the per-input-queue memory limit)

        Activity

          People

          • Assignee:
            bryanthompson bryanthompson
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: