Is there some way to configure the polling interval into SVN?
We are having issues with the stability of our SVN repository, primarily due to issues with an older version of the WANdisco MultiSite product we are using for replication to a DR repository and user failover. It will take us several weeks to upgrade, due to a variety of reasons I won't go into here.
However, WANdisco support is telling us that one contributor is the user that Cruise is using on one pipeline to deploy an appllication. That user is apparently averaging about one SVN transaction per second or so, all around the clock. They are asking us if that user can cut back on the request rate.
From our standpoint, polling once a minute (or even every few minutes) should be more than adequate for our purposes.
TIA,
Steve Elkind
Go Version: 2.0.0(11407-bdc7f35f9bc0)
Comments
1 comment
Hi Steve,
The default polling interval for an SCM material in Go is 60 seconds. This setting is global for the entire Go server.
We poll the SCM for latest revision for each unique repository. So for a single pipeline with a single SCM, we would poll only once every 60 seconds. As per your post, one request to SCM per second for the same repository from Go seems abnormal. Can you confirm that these requests are from Go server and not from any of your scripts? If you suspect they are from Go, please attach the go-server.log file so that we can investigate this further.
If you do want to configure the polling interval and see if it helps, we have an undocumented way of doing it. You can specify the property "cruise.material.update.interval" in the startup scripts (server.sh or server.bat) and restart the server. For example, you need to add "-Dcruise.material.update.interval=180000" to the command that Go server starts with to setup a polling interval of 3 minutes.
Regards,
Rajesh
Please sign in to leave a comment.