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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Hight CPU usage after updating from Bitbucket v6.10.16 to v7.17.4


We recently updated Bitbucket from v6.10.16 to v7.17.4 and noticed that the CPU is increased by 40%. Initially we thought it was a reindex issue and it needs some time but even after 48 hours and doing reindex twice I see that the CPU is way higher than what it was earlier. For reindex I  deleted the old index and started the index process b curl call. I also have set the -Xms1g-Xmx1g in the homedirectory/shared/search/jvm.options file, which was standard for previous version as well. Any help is greatly appreciated. Please let me know if there is anything I can try out.


1 answer

It appeared that moving from 6.x to 7.x needed a ES reindexing and surprisingly that  took almost 2 days. That was the  reason CPU was utilized fully. We  ended up  adding temporary CPU to  the server and  when reindex was  complete the CPU   went back to normal.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events