Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jiradc - R4J plugin cause exponential growth of AO_242870_REVISION_HISTORY & AO_242870_ISSUE_REVISIO

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.

2 answers

2 accepted

0 votes
Answer accepted
Bibek Behera Community Leader Feb 23, 2021

@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

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. 

0 votes
Answer accepted

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!

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.

Welcome!

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.4
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you