Skip to main content

Error message

You might also see java.lang.OutOfMemoryError or java heap space in the error text. This error can appear when using the following components: Jira Load, OData Query, PostgreSQL Load, Salesforce Load, and SQL Script.

Explanation

The Maia runner ran out of memory while running a component in your pipeline and couldn’t finish. This is most often caused by large extracts, or by many tasks running at once on one Maia runner.

Potential causes

  • A connector pulled large pages or result sets into memory. This is common with Salesforce, PostgreSQL, OData, and Jira extracts.
  • Several heavy pipelines ran on the same Maia runner at the same time.
  • The Maia runner‘s memory allocation is small for the workload.

Resolve the error

  1. Find the failed component in the pipeline run. That’s the one running when memory ran out.
  2. Reduce the page size or batch size on that component, or add filters so each run extracts less data.
  3. Lower concurrency: reduce parallel loop iterations and stagger heavy schedules so they don’t overlap.
  4. Increase the Maia runner‘s memory, or add instances and spread heavy pipelines across them.
  5. Re-run the pipeline.
  6. If you still need help, contact Maia Support and include the items listed below.
    • The Maia runner ID.
    • The component and its page or batch size settings.
    • The Maia runner‘s memory allocation.

Prevent future errors

To prevent this error occurring again:
  • Use incremental loads instead of full extracts where the source supports it.
  • Monitor Maia runner memory and set alerts before it reaches the limit.