Re: JNLP Slave Behavior upon Server Bounce
The jobs do die when the server goes down. On Thursday, September 6, 2012 5:59:40 AM UTC-7, Mandeville, Rob wrote: Just to be sure: they don’t abort their jobs in this case? --Rob *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *domi *Sent:* Thursday, September 06, 2012 8:58 AM *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: JNLP Slave Behavior upon Server Bounce Hi Rob, yes they are, the slaves automatically reconnect to there master as soon as its available again. Domi On 06.09.2012, at 13:10, Mandeville, Rob rmand...@litle.comjavascript: wrote: I’m running a fairly extensive Jenkins installation with about 120-140 slave nodes, almost entirely on Linux (as is the server). The server has been hanging and taking up 100% CPU on its server from time to time, so I’ve had to bounce the server. With 12-hour test cycles, this can be…disruptive. I am trying to diagnose that problem, but while I’m doing that, I’m also trying to figure out a way to be able to bounce the server and keep the jobs running. Currently, all slaves have a launch method of “Launch slave via execution of command on the Master”, and said commands are SSH jobs. So, when I kill the Jenkins server, its 120+ SSH jobs die because they’re subordinate processes, killing the slaves and any jobs running on them. I know that you can launch JNLP slaves so that they aren’t subordinate jobs, and won’t get automatically killed by Linux when you kill the server. So my question is: If I have a JNLP slave running a job and its Jenkins server dies, will it re-establish the connection and continue the job it was running when the server comes back up? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
JNLP Slave Behavior upon Server Bounce
I'm running a fairly extensive Jenkins installation with about 120-140 slave nodes, almost entirely on Linux (as is the server). The server has been hanging and taking up 100% CPU on its server from time to time, so I've had to bounce the server. With 12-hour test cycles, this can be...disruptive. I am trying to diagnose that problem, but while I'm doing that, I'm also trying to figure out a way to be able to bounce the server and keep the jobs running. Currently, all slaves have a launch method of Launch slave via execution of command on the Master, and said commands are SSH jobs. So, when I kill the Jenkins server, its 120+ SSH jobs die because they're subordinate processes, killing the slaves and any jobs running on them. I know that you can launch JNLP slaves so that they aren't subordinate jobs, and won't get automatically killed by Linux when you kill the server. So my question is: If I have a JNLP slave running a job and its Jenkins server dies, will it re-establish the connection and continue the job it was running when the server comes back up? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
RE: JNLP Slave Behavior upon Server Bounce
Just to be sure: they don't abort their jobs in this case? --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of domi Sent: Thursday, September 06, 2012 8:58 AM To: jenkinsci-users@googlegroups.com Subject: Re: JNLP Slave Behavior upon Server Bounce Hi Rob, yes they are, the slaves automatically reconnect to there master as soon as its available again. Domi On 06.09.2012, at 13:10, Mandeville, Rob rmandevi...@litle.commailto:rmandevi...@litle.com wrote: I'm running a fairly extensive Jenkins installation with about 120-140 slave nodes, almost entirely on Linux (as is the server). The server has been hanging and taking up 100% CPU on its server from time to time, so I've had to bounce the server. With 12-hour test cycles, this can be...disruptive. I am trying to diagnose that problem, but while I'm doing that, I'm also trying to figure out a way to be able to bounce the server and keep the jobs running. Currently, all slaves have a launch method of Launch slave via execution of command on the Master, and said commands are SSH jobs. So, when I kill the Jenkins server, its 120+ SSH jobs die because they're subordinate processes, killing the slaves and any jobs running on them. I know that you can launch JNLP slaves so that they aren't subordinate jobs, and won't get automatically killed by Linux when you kill the server. So my question is: If I have a JNLP slave running a job and its Jenkins server dies, will it re-establish the connection and continue the job it was running when the server comes back up? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
Re: JNLP Slave Behavior upon Server Bounce
That I'm not 100% sure, but I think the jobs do get killed - even though the saves are not dead. Domi On 06.09.2012, at 14:59, Mandeville, Rob rmandevi...@litle.com wrote: Just to be sure: they don’t abort their jobs in this case? --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of domi Sent: Thursday, September 06, 2012 8:58 AM To: jenkinsci-users@googlegroups.com Subject: Re: JNLP Slave Behavior upon Server Bounce Hi Rob, yes they are, the slaves automatically reconnect to there master as soon as its available again. Domi On 06.09.2012, at 13:10, Mandeville, Rob rmandevi...@litle.com wrote: I’m running a fairly extensive Jenkins installation with about 120-140 slave nodes, almost entirely on Linux (as is the server). The server has been hanging and taking up 100% CPU on its server from time to time, so I’ve had to bounce the server. With 12-hour test cycles, this can be…disruptive. I am trying to diagnose that problem, but while I’m doing that, I’m also trying to figure out a way to be able to bounce the server and keep the jobs running. Currently, all slaves have a launch method of “Launch slave via execution of command on the Master”, and said commands are SSH jobs. So, when I kill the Jenkins server, its 120+ SSH jobs die because they’re subordinate processes, killing the slaves and any jobs running on them. I know that you can launch JNLP slaves so that they aren’t subordinate jobs, and won’t get automatically killed by Linux when you kill the server. So my question is: If I have a JNLP slave running a job and its Jenkins server dies, will it re-establish the connection and continue the job it was running when the server comes back up? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
