My reading of the code indicates that the timeout value is set by "kexTimeout" in com\trilead\ssh2\Connection.java at line 693. That appears to be set in SSHLauncher.openConnection():1184. The value we're using for 'launchTimeoutMillis' should be 15000, assuming that it comes from "Startup Idle" in the slave configuration (we enter '15', since the help says that the units are seconds). The machine we're using has 64gb of RAM, and 24 cores. It's possible that it's a performance issue, but I doubt it. I'll try monitoring that a bit...
Thanks for your response. On Wednesday, February 6, 2019 at 11:14:53 AM UTC-5, Ivan Fernandez Calvo wrote: > > >Jenkins and the VMs are all running on the same machine, so network > activity shouldn't be an issue. > > network is not an issue, but performance response, Could it be? it is not > a good idea to run the Jenkins Master and Agents in the same machine, if > you use Docker container and you do not limit the resources used by each > container (memory and CPU), they will fight for resources and some of them > will be killed by docker with a nice OOM. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/21922cc3-652d-4fee-b6d6-b90fef7a4bba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
