Server slow to pickup connected agents after server shutdown

waiting since 5mins after tomcat restart.. then they all came back at once.. is there any property to modify "agent-rescan-interval"?

5 comments

There is no such property. The slowdown can be caused by upgrade process (if you installed new TeamCity server). Other than that if server is up and running and responding to HTTP requests agents should connect relatively quickly.

Could you please describe your setup in more details? What TeamCity server do you use? How many agents do you have? Please take a look at agent and server logs, there should be messages related to agent registration.

--
Pavel Sher

0

There is no such property. The slowdown can be caused by upgrade process (if you installed new TeamCity server). Other than that if server is up and running and responding to HTTP requests agents should connect relatively quickly.


this happened both after server upgrade as well as after restart of the webapp - so "relatively quickly" is about 5 min ;) I was just wondering what interval TC server is using internally (hardwired?) to broadcast heartbeats..

Could you please describe your setup in more details? What TeamCity server do you use? How many agents do you have? Please take a look at agent and server logs, there should be messages related to agent registration.



TeamCity Enterprise 4.0 EAP (build 7601)
about 9 agents online avg

Greetings,

Yann

Edited by: Yann Cébron on Sep 8, 2008 10:37 AM

0

Server pings all connected agents each 10 seconds. But server does not initiate agent registration, instead registration is initiated by agent itself, so in your case the whole process of agent registration probably takes too much time. Please take a look at agent logs, there should be messages when agent initiated registration process and when registration process finished (when agent got id from the server), something like:
INFO - buildServer.AGENT.registration - Registering on server: [name: Default agent, ownAddress: , ownPort: 9092, buildId: ]]>, availableRunners: ]
INFO - buildServer.AGENT.registration - Registered: id:145, authorizationToken:d1713a16a461cbdec1a1f9b10e9a4831

--
Pavel Sher

0

Thanks for the clarification. Still I suggest to speedup this process in general, I don't see a reason why it should take this long.

0

The process depends on network speed and current server load. When agent connects to the server server tries to ping agent before registration (to detect firewall) and since this is network operation it can take some time. Another point is that usually agents are registering right after the server start-up when server load can be high because caches are not loaded yet and when all clients (IDE plugins and browsers) are trying to connect to the server too.

It would be fine if you'll find some time and make a CPU snapshot from your server with help of our plugin: http://www.jetbrains.net/confluence/display/TW/Server+Profiling when agents are registering.

--
Pavel Sher

0

Please sign in to leave a comment.