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

I uninstalled JEMH and re installed it after the re install jira suddenly goes very slow. The cpu usage of jira peaks at 80+% and it is impossible to use jira. If i remove JEMH the CPU usage of jira goes down to normal levels. Is this a issue you have ever enountered before ? I removed all the settings i had in the profile to be sure that it wasnt a issue with my settings

3 answers

1 accepted

1 vote
Answer accepted

Hi Daniel,

If you've uninstalled and reinstalled, you will get the latest compatible version. In doing this, its possible some schema upgrade tasks run that take time to complete. The specific type of data that needs to be updated is:

  • Audit History
  • Notification History

If you have a busy instance and/or have retained a large amount of audit history data there will be a lot of data to upgrade. The upgrade process is single threaded so on a multi-cpu instance should onyl occupy a single core and should not result in overall performance degredation.

To avoid this, the audit history retention needs to be set lower, perhaps days. To be able to do that, uninstall the current version, and back off to an ealier one (if this is part of an overall JIRA upgrade, making that impossible due to compatibility, you'll need to do a manual table purge for JEMH data, details of which are on the wiki.

Let me know if that doesnt resolve the problem you see?

This setting looks dangerous. Is it this that causes my problems ?

com.javahollic.jira.emh.service.scheduling.JEMHJobSchedulerImpl:job

com.atlassian.sal.jira.scheduling.JiraPluginSchedulerService
Delay: 0 minutes
pluginJobName: com.javahollic.jira.emh.service.scheduling.JEMHJobSchedulerImpl:job
repeatInterval: 1000
initiallyFired:

true

Hi the problem is now fixed. To be honest i am not sure what i did to fix it.

1) I update the universal plugin manager

2) installed older version of JEMH

3) did re indexing

Now JEMH is running as our Mail handler

Hi Daniel,

I suspect you have a lot of audit history data, that could do with purging, once cleared, an upgrade task would have less to do, would not present high CPU load?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in United States

Welcome new members!

Wow, I got swamped and now that I've finally gotten my head back above water, I find we have several new members! Welcome @Darren Keith lowman , @Amanda Babb , @Luis Zapata , @Joli Holmes , and @bh...

31 views 0 2
View post

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