EazyBI Scheduled import fails

We have an JIRA Server Instance with about 20K issues.
JVM memory is set to 2GB.
The scheduled import fails on the following error: org.olap4j.OlapException: mondrian gave exception while executing query / OutOfMemory used=1343887376, max=1431830528

Should we increase the JVM Memory to 4GB?
Note:
When I empty the cube and import it manually, the import succeeds.
When I don’t empty the cube and import manually, the import fails.

[5C02C58F:5017326b] e[1me[31m[pivot_table.query.eazybi]e[0m (44.0ms) {:account_id=>2, :user_id=>1054, :cube=>“Issues”, :cube_table=>“jira_issues_measures”}
2017-10-16 02:44:51 +0300 ERROR: SELECT NON EMPTY [Status].[Status].Members ON COLUMNS,
2017-10-16 02:44:51 +0300 ERROR: NON EMPTY [Assignee].[User].Members ON ROWS
2017-10-16 02:44:51 +0300 ERROR: FROM [Issues]
2017-10-16 02:44:51 +0300 ERROR: WHERE ([Time].[All Times], [Sprint].[SQA board].[Auto Sprint 13 (23.7 - 10.8)], [Project].[SW QA Automation], [Measures].[Issues created])
2017-10-16 02:44:51 +0300 ERROR: [5C02C58F:5017326b] e[1me[31m[Mondrian::OLAP::Error]e[0m org.olap4j.OlapException: mondrian gave exception while executing query / OutOfMemory used=1343887376, max=1431830528 for connection: Jdbc=jdbc:jtds:sqlserver://iivdbprod2.indigo.co.il:1433/eazybi_jira; JdbcDrivers=net.sourceforge.jtds.jdbc.Driver; UseContentChecksum=true; CatalogContent=’<?xml version="1.0" encoding="UTF-8"?>
2017-10-16 02:44:51 +0300 ERROR: <Schema description=“Last import at 2017-10-16T02:37:08+03:00” measuresCaption="%
{cubes.measures.caption}

Hi Ran,

You may set JVM memory to 4GB if you have some issues with memory. 2GB of JVM memory is a minimal requirement to run eazyBI.

From your description, it seems there are two separate problems - one related to data import and another related to the specific report.

  1. Regarding data import, after failed import, please collect eazyBI log files and send them to the eazyBI support for an investigation.

  2. Regarding report which times out, please export report definition of the failing report and send it to the eazyBI support so we can suggest improvements.

Best,
Zane Baranovska / support@eazybi.com

Thank you Zane.
We have found in the logs that the failure is actually due to something else: a duplicate issue record in the issues table. We used some workaround to delete the duplicate error and now it’s ok.
Thanks