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

Add a Tip to LOOKUP JOIN about rhs memory limits

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.4.0
    • Component/s: Documentation
    • Labels:
      None

      Description

      Would be nice to include something about LOOKUP JOIN to ephasize that the rhs must fit into memory on every node.

      for example:

      If your job is spilling to disk or if you get
      “error: 1301: Pool memory exhausted: pool id 4194667 exhausted, requested 1 heap(1216/4294967295) global(1216/1216) (in Lookup Join”

      It means the RHS is too big and lookup join should not be used…

        Attachments

          Activity

            People

            • Assignee:
              jamesdefabia Jim DeFabia
              Reporter:
              jamesdefabia Jim DeFabia
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: