Hi all, I'm observing a problem with our new Jenkins master, running on an Ubuntu VM on a high-spec Azure instance - latency between master and workers is *crazy* high. Like 30 plus seconds: https://jenkins.mono-project.com/computer/. The SSH-based workers can generally survive that, but the JNLP workers time out and kill running jobs (we're using JNLP for non-cloud workers as it makes our network management way simpler). And Jenkins does a pretty dreadful job of keeping track of whether workers are connected or not, so I end up having to restart the master to kick-start things. It's basically a nightmare.
It seems we're not the only people running Jenkins on Azure showing obscene response times, e.g. http://dotnet-ci.cloudapp.net/computer/ - so the question is whether anyone else on the list has observed this, or (even better) resolved it. The master isn't under high IO, network, memory or CPU load, seems well supplied with entropy; and the failures don't seem to correlate with Java GC pauses; so I'm not sure where to point the finger. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CACyRP71rAKJ3Q7k0NqbAY5M3mZivbxbhoHUuPDjspTAkv%2Bvvcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
