Data360 Analyze

 View Only
Expand all | Collapse all

Java heap space issue for lookup transformation -- Urgent -- Data3Sixty Analyze

  • 1.  Java heap space issue for lookup transformation -- Urgent -- Data3Sixty Analyze

    Employee
    Posted 12-25-2019 01:10

    Hi Team,

     

    We are facing below error at lookup transform in two of our Jobs, We have tried checking below things before reaching out to you guys,

     

    1) Updated the JavaMaxHeadSize property with values like 4g, 5g, 4096M, 8192M and try running the job but we still face the same error and the job is not getting completed because of the same.  (this is in reference to post https://support.infogix.com/hc/en-us/articles/360024709093-OutOfMemory-Error-in-Data3Sixty-Anlayze)

    2) We tried restarting the server on which Data3Sixty is hosted but still, the problem persists. 

     

    Can you please check why is this happening and provide us a workaround to get over this issue? Request you to consider this as an urgent request because we have scheduled jobs running and we might lose some precious source data if we cannot fix it as soon as possible. 

     

     

    Unexpected error occurred during processAll while running the node: java.lang.OutOfMemoryError: Java heap space.
    Error code: brain.unexpectedNodeErrorDuring

    Raised on: Dec 25, 2019 at 11:52:23 AM

    Detail: com.lavastorm.brain.execution.java.node.NodeWrapper.nodeProcess
    (NodeWrapper.java:586)

     

    Attached files

    Java_Heap_Space_Issue dim test run.jpg
    Two Jobs for which Lookup Transform giving java heap space issue.lna
    java_head_space_issue_dim_jira_defect_table.jpg

     



  • 2.  RE: Java heap space issue for lookup transformation -- Urgent -- Data3Sixty Analyze

    Employee
    Posted 12-26-2019 14:38

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    If you don't have any duplicates in your join criteria, can you try replacing the Lookup with a Join? Set it to Left Inner and it should perform the same. I attached 2 screenshots that have a Lookup erroring out similar to your's, whereas the Join did not. I changed my Lookup JvmMaxHeapSize to 4G to give it enough memory to operate without erroring out, but note that I did not have to change the default value on the Join node.

     

    Attached files

    MaxHeapError_on_Lookup.png
    4G_on_Lookup.png