Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
preston-settle
Contributor
Contributor

Extraction error: [accumulator] com.stitchdata.target-stitch-avro.accumulator-thread - accumulator thread is dying - Java heap space

[accumulator] com.stitchdata.target-stitch-avro.accumulator-thread - accumulator thread is dying - Java heap space
 
Has anyone encountered this error?
 
We are using the Google Cloud SQL PostgreSQL Integration writing to Snowflake as the destination. It is able to load some rows every now and then but keeps giving this error on each extraction run.
Labels (2)
1 Solution

Accepted Solutions
Xiaodi_Shi
Employee
Employee

Hello @preston-settle 
Is this a local connection you’re running? As far as we know, our production memory limit is 6G.
You can probably tweak some advanced options, like itersize.

We have two non-customer-facing settings we can help to set. Those are the Incremental limit and the Itersize values.

For more information, please refer to this KB article:

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Discovery-succeeded-Tap-failed-w...

Best regards

Sabrina

View solution in original post

1 Reply
Xiaodi_Shi
Employee
Employee

Hello @preston-settle 
Is this a local connection you’re running? As far as we know, our production memory limit is 6G.
You can probably tweak some advanced options, like itersize.

We have two non-customer-facing settings we can help to set. Those are the Incremental limit and the Itersize values.

For more information, please refer to this KB article:

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Discovery-succeeded-Tap-failed-w...

Best regards

Sabrina