Data360 Analyze

We are running into an error when trying to Aggregate Node under the Aggregation and Transformation section.  It is giving us this error:  Unexpected error occurred during process All while running the node: java.lang.OutOfMemoryError: Java heap space.

We followed the instructions here from the community:  https://support.infogix.com/hc/en-us/articles/360024709093-OutOfMemory-Error-in-Data3Sixty-Analyze

And increased the value from 8 gb to 14 gb.  We are still getting the error, we have traced the issue to the Aggregate node.  {See below Image 1 and image 2}

But also, we have noticed that when something errors in Data3Sixty, it abandons tasks in the task manager.  {See below image 3 and image 4} Is there a setting to make sure that if a scheduled workflow fails, that we can also send a command to kill the tasks?  We bounced the server and it got rid of all the PostGreSQL tasks.

I have searched the community, but could not find an answer.

Attached files

image1_Aggregate_error_20191003.png
image2_Aggregate_error_20191003.png
image3_Task_error_20191003.png
image4_Task_error_20191003.png

The Postgres tasks are created by PostgreSQL as required and are are used by the Analyze database. These tasks are not associated with the running of nodes. 

A number of issues relating to Out Of Memory errors have been fixed recently. Can you let us know which version of the product you are using? You can get the details using the information (i) button on the menu --> About Data3Sixry Analyze.

Hi Adrian,

Version: "3.4.0.4934"

Also the PostgreSQL tasks are a separate issue.  There seem to be many orphaned tasks, left over from our night time schedule of Extractions.  We have many REST APIs scheduled to run in the night, and then along with the REST APIs, the TRANSFORM and LOAD of data from our staging tables to the Data Warehouse.

We are finding that if an scheduled ETL fails during the night, it orphans a task in the Windows Task Manager.  We wanted to know if there was a setting in Data3Sixty to kill those tasks.

Thanks!

Kyle

Update:

We are using the Aggregate for strings, and it was recommended to us by Paul from Infogix, to use the Transform node instead.  We are currently looking into this method and will reporting on its functionality.