Hi, James, thank you for explanation! I fugured that too... Won't make this misinterpretation in the future now. Also, that'd be very bad desing and I doubt that community would just let this in. So the issue is some place else. I wonder if the instance has too many Jenkins masters running at once... Other do not experience this slowness though Anyway, thanks for help, guys!
Cheers, Jan 2015-09-28 12:54 GMT+02:00 James Nord <[email protected]>: > in any other way than the ping thread is terribly slowing down Jenkins by >> causing other threads to wait for it: > > > No the ping thread is sleeping. The executor thread is waiting on the > channel to give it more data. > > - you got a little confused due to the fact that the ping thread has the > name of the channel Object in its threads name (which is the same Object > that the executor is wating for...) > > /James > > On Thursday, September 24, 2015 at 3:21:33 PM UTC+1, Jan Lutenko wrote: >> >> Hi, >> >> I'm not really familiar how this works internally, but looking at thread >> dump in Jenkins I can not interpret this >> in any other way than the ping thread is terribly slowing down Jenkins by >> causing other threads to wait for it: >> >> Short background: Jenkins 1580.3, running on x64 RHEL with 4 cores and 24 >> G RAM. Not the only instance on master host, other seem to be feeling >> better, I suspect this pinging thread to be the cause of long time page >> loading. >> >> Not listing any further info not to overload someone who's reading this >> with useless information.. At the moment. >> >> >> Ping thread for channel hudson.remoting.Channel@32a6cf5b:<host> >> >> "Ping thread for channel hudson.remoting.Channel@32a6cf5b:<host>" Id=108 >> Group=main TIMED_WAITING >> >> at java.lang.Thread.sleep(Native Method) >> >> at hudson.remoting.PingThread.run(PingThread.java:91) >> >> >> The rest of thread dump (specifically jobs) looks more or less like this: >> >> Executor #6 for <host> : executing <job> #<build_number> / waiting for >> hudson.remoting.Channel@32a6cf5b:<host> >> >> "Executor #6 for eselivm2v759l : executing mct_up_check #2004 / waiting >> for hudson.remoting.Channel@32a6cf5b:<host>" Id=625627 Group=main >> TIMED_WAITING >> >> on hudson.remoting.UserRequest@7654c0aa >> >> at java.lang.Object.wait(Native Method) - waiting on >> hudson.remoting.UserRequest@7654c0aa >> >> at hudson.remoting.Request.call(Request.java:146) >> >> at hudson.remoting.Channel.call(Channel.java:751) >> >> at >> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) >> >> >> at com.sun.proxy.$Proxy56.join(Unknown Source) >> >> at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) >> >> at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) >> >> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) >> >> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) >> >> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) >> >> at >> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) >> >> >> at hudson.model.Build$BuildExecution.build(Build.java:199) >> >> at hudson.model.Build$BuildExecution.doRun(Build.java:160) >> >> at >> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) >> >> >> at hudson.model.Run.execute(Run.java:1745) >> >> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) >> >> at hudson.model.ResourceController.execute(ResourceController.java:89) >> >> at hudson.model.Executor.run(Executor.java:240) >> >> Can someone please confirm that my logic here is right/wrong? Also, how >> can I disable the ping thread? >> I know that adding -Dhudson.remoting.Launcher.pingIntervalSec=-1 to >> slave call and a similar >> option to master start up can stop the thread from pinging, but will it >> be turned off then? >> >> Any help on this would be very much appreciated as I am stumbling on this >> issue not for the first time and hitting a wall as well again. >> >> Thank you and Best Regards, >> Jan >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/eQTbvl1UPCw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/25dfbc23-8313-48a3-8616-a9b4033917f3%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/25dfbc23-8313-48a3-8616-a9b4033917f3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Z poważaniem, Jan Lutenko -- 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/CADzPo267w7xERZD38UZzReT%3DcL-KBOWET3%3DvUDRT%2BHF7EycmBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
