Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

SVN repository scanning stuck in Fisheye

Hi,
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,

Ana

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

222 views 2 1
Read article

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