You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey there,
since we upgrade fisheye from 3.7 to 3.8.1 in gradle open source project, We're seeing high cpu load constantly caused by the fisheye process. We havn't changed anything in configuration and just using one incremental-indexer thread. Is anybody else seeing this issue. We would really like to track this down. any help and advice is highly appreciated as our server is now running with 98% caused by fisheye. restarting doesn't solve the issue. is there anything I can look for in the debug logs that might give me a hint?
cheers,
René Gröschke
Hi,
The best way to figure out what is going on would be to take some thread dumps during the high CPU load, or to use a tool such as jvmtop to get a better idea of which threads are taking up a lot of CPU.
We have some instructions here on how to generate thread dumps.
It could be for example, this open bug:
https://jira.atlassian.com/browse/CRUC-6593
However, there are many possible causes, so the best way forward would be to get a few sets of thread dumps at a 15 second interval during high CPU load. Please open up a support ticket if you'd like us to investigate further.
Best regards,
Dave Lahn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.