Fisheye multiple connections to SVN

Question

We have a fisheye server recently installed and I noticed since we installed it my SVN service sporadically drops. In log I found this:

Deactivating service svn due to excessive incoming connections.  Restarting in 10 seconds.

I checked ixnetd.conf file and it is the default. Temporarily I've bumped up the cps from 50 to 250 to resolve.  A packet capture later I can see that fisheye has a great number of open connections on our SVN server. Is this expected behavior or is something misconfigured?

Conor · Answer

FishEye can indeed overload the default cps limits enforced by xinetd. Please refer to

https://confluence.atlassian.com/pages/viewpage.action?pageId=298977097

It is probably best to set a connection limit in the FishEye configuration to prevent FishEye from overloading the server. You may want to try different settings to get the balance between FishEye load and speed of indexing right.

Note that FishEye enforces its connection limit on the Subversion operation level which may not exactly match the connection rate at the svn protocol level but should be within the same ballpark.

More information on the setting is here: https://confluence.atlassian.com/display/FISHEYE/Subversion where it is referred to as a throttle.

Nick · Answer

How many connections are you seeing FishEye has open with your SVN server ? With just a single repository, I would not expect more than 1 or 2 connections to be open and active at any one time.

FishEye needs to do an 'initial index' - replay all commits in your repository, however once that is complete, it will poll you repository for new commits. This defaults to 1 minute, however You can use a much larger value, and reduce latency for new commits to near zero if you configure an svn SCAN NOW commit hook https://confluence.atlassian.com/display/FISHEYE/Configuring+commit+hooks

Timothy Trulis · Answer

one single repository.