Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-29785

Bare-metal systems with slavesPerNode>1 are not automatically splitting available memory.

    XMLWordPrintable

Details

    • Regression
    • Status: Resolved
    • Not specified
    • Resolution: Fixed
    • None
    • 9.0.20, 8.10.54, 8.12.32
    • Thor
    • None

    Description

      Regression was introduced in 8.4 (https://track.hpccsystems.com/browse/HPCC-26600)

      If no globalMemorySize setting and slavesPerNode is >1, the available memory was and should automatically be subdivided between the workers.

      HPCC-26600 broke that.

      I think it hasn't been noticed to date because it is common practice to manually specify the globalMemorySize, mainly because it can't be automatic in systems that have >1 Thor instance running on the same h/w.

      Attachments

        Issue Links

          Activity

            People

              jakesmith Jake Smith
              jakesmith Jake Smith
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: