Go server polls for changes to all materials of 'Auto Triggered' pipelines. By default, polling occurs every minute and ten materials at a time. The polling interval and the number of materials to be polled simultaneously are configurable.
Go uses SCM commands to poll for changes. For example, to check for any new changes in SVN repository the following command is used:
svn log --non-interactive --xml -v -r HEAD:'revision' 'repository-URL'
The SCM command used by Go server can hang with no output. Invalid configuration, network issues, console input block are some of the causes for such a situation. Such scenarios cause pipeline scheduling delays and also lead to performance degradation
Such a scenario is notified to the users by a warning in Server Health; when clicked shows a message similar to the one below.
When you see warning messages like the one above
On linux installations of Go server, add the following line to /etc/default/go-server.
export GO_SERVER_SYSTEM_PROPERTIES='-Dmaterial.update.inactive.timeout=20'
The above configuration sets the time that Go server uses to determine if a material update is possibly hung, to 20 minutes.
On Windows, add the following line in the wrapper-properties.conf file in the config folder of the Go server installation where x is 1 more than the highest number in wrapper-server.conf and wrapper-properties.conf combined.
wrapper.java.additional.x='-Dmaterial.update.inactive.timeout=20'
The above configuration sets the time that Go server uses to determine if a material update is possibly hung, to 20 minutes.