Jiradc - R4J plugin cause exponential growth of AO_242870_REVISION_HISTORY & AO_242870_ISSUE_REVISIO

[Divya Vishnumurthy]

After we installed R4J plugin on Jira datacenter 8.5.4 we saw exponential growth (103 million rows) of AO_242870_REVISION_HISTORY and AO_242870_ISSUE_REVISION  tables.

Our XML import fails because the size is too huge.

Questions:

1) Do yo know of any clean up scripts that I can run to reduce the table size?

I have a support request with R4J vendor. But no workaround yet.

2) I removed revision history table rows from the XML activeobjects.xml and tried to import. It still fails, which other tables rows can I remove to reduce the size of the XML backup file.

[Bibek Behera · Accepted solution]

@Divya Vishnumurthy ,

I would suggest you to wait for the inputs from the plugin vendor. It is wise to follow a tested approach from the plugin vendor rather then trying workarounds.

Please post the outcome here so that other's can also get an idea about how to limit the size.

Regards,

Bibek

[Divya Vishnumurthy]

This answer is not helpful. yes I will follow the vendor steps, but the question is if someone has already done this before and can help me. 

[Joshua Sneed _ Contegix · Accepted solution]

Hi Divya,

Modifying the export is not recommended and is likely to fail. The best path forward is to wait for the vendor, as Bibek stated, and go from there. Ideally, they will publish an update that you can install before exporting and all will be well.

Alternatively, you can drop that table or the tables for that plugin prior to exporting, but that almost ensures data loss and is not a clean way forward. Cheers!

[Divya Vishnumurthy]

The revision history clean up was included in R4J 4.4 release earlier but now they removed it fro m 4.4 scope. https://easesolutions.atlassian.net/wiki/spaces/REQ4J/pages/1424556175/4.4+BETA

So we are left with no workaround and a growing database. I tried to search online but couldn't find anything useful. Thank you for your response.

[Joshua Sneed _ Contegix]

Welcome!

Contact the vendor, ask for a workaround, and lean on them until they fix their app or provide a solution. Cheers!