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

SVN repository scanning stuck in Fisheye

I recently added way to many SVN repos (>5555) to our Fisheye (V4.4) instance. I am using powerful system with (62G RAM; 8core; 40GXms & 40Xmx) where the instance is installed. However the scanning is still stuck, it's been more than 7 days the scanning is 0%. We are using https:// protocol, though I am aware that if we use SVN:// or File:// protocol the performance may increase, but at this moment we only want to use https:// protocol.  Initial indexing threads  is set to '4' and  FishEye and Incremental indexing threads is set to '5'. Block size is set to '800' just to reduce the time it takes to scan the repository. As a workaround i stopped all '5555' repos and ONLY started one to check if it expedite the scanning process, but no LUCK. Still stuck at 0% and i really have no idea what next. Also i dont find any log entries about this. oser501222 scanning stuck.JPG

1 answer

1 accepted

0 votes
Answer accepted
Ana Retamal Atlassian Team Aug 22, 2018

Hi Manu, 

We've seen that there's been already several support tickets open in relation to this issue, so my advice would be to follow up on those so that way we'll be able to keep the history of your instance and have access to the steps that have been previously taken to continue further with this troubleshooting.

Having said this, please note that we warned you against this migration and the problems faced now are or might be a consequence of the repositories having been consolidated into a single instance. 


For further assistance, please open a new ticket and reference the previous cases so our team has full context of the situation and can assist you more effectively.

If you need anything else, please let us know!

Best regards,


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events