Needed suggestions for Jenkins Master/Slave architecture

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
BTH
Reply | Threaded
Open this post in threaded view
|

Needed suggestions for Jenkins Master/Slave architecture

BTH
Hello Folks!

I'm about to set up New Jenkins cluster with Master/Slave model. Actually, we already have Jenkins master-only running but it's usually faces run out of memory issue.

I've read all the recommended on the official, however there are some details missing there.

1. Please suggest for storage for both Master and Slave. Currently our Master-only Jenkins uses huge disk spaces (~200GB) and it tends to increase along with the number of new jobs.

My question is where does ./workspace, ./jobs and ./caches (most biggest directories) under $JENKINS_HOME will store? in Master or Slave?

2. If I mark Master as drain node (not executing job), so my master can possibly has a minimal resources e.g. CPU 1vCPU and 4GB or less number of memory ?

**for my current Master-only Jenkins, we have 30GB memory/200GB

3.  If there any issue or concerns from migrating Master-only to Master/Slave ? 

Any suggestion would be appreciated :)

Cheers,

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEaEQi%2BxfiHndc7%3Dnr3dtjaPEF_A__tc3-dkyRvsY5%2B0%3D1Pdmw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

RE: Needed suggestions for Jenkins Master/Slave architecture

Jérôme Godbout

Hi, there isn’T much constraint except the setup when moving from master only to master/slave. Only SSH to be setup and here you go. As for the disk space, the workspace is not automatically clean, you might want to clean the working directory before you end your pipeline (after gathering all the wanted information).  This will save space on the slave hard disk. To test your setup, you can use the same machine for you Jenkins slave as the master one, it will work and after you only need to setup additional slave on other machines.

 

Jenkins keep the build information and the project folder will grow over time. You can setup the project to only keep X items or items from a specific length of time. That will reduce the master size.

 

But keep in mind the slave Harddrive will be stressed a lot, they will have a short life time. I backup the master project and have a reliable setup with raid there. Slave are burnable, you don’t really care, fast enough to do the job, died, just put back a new image that kickstart a slave with a new harddrive and up you go.

 

Jérôme Godbout
Software / Firmware Lead

C: (581) 777-0050 
O: (418) 800-1073 ext.: 109  
[hidden email]

dimonoff.com   |    amotus.ca

 

From: [hidden email] <[hidden email]> On Behalf Of banthita limwilai
Sent: February 2, 2021 3:44 AM
To: [hidden email]
Subject: Needed suggestions for Jenkins Master/Slave architecture

 

Hello Folks!

 

I'm about to set up New Jenkins cluster with Master/Slave model. Actually, we already have Jenkins master-only running but it's usually faces run out of memory issue.

 

I've read all the recommended on the official, however there are some details missing there.

 

1. Please suggest for storage for both Master and Slave. Currently our Master-only Jenkins uses huge disk spaces (~200GB) and it tends to increase along with the number of new jobs.

 

My question is where does ./workspace, ./jobs and ./caches (most biggest directories) under $JENKINS_HOME will store? in Master or Slave?

 

2. If I mark Master as drain node (not executing job), so my master can possibly has a minimal resources e.g. CPU 1vCPU and 4GB or less number of memory ?

 

**for my current Master-only Jenkins, we have 30GB memory/200GB

 

3.  If there any issue or concerns from migrating Master-only to Master/Slave ? 

 

Any suggestion would be appreciated :)

 

Cheers,

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEaEQi%2BxfiHndc7%3Dnr3dtjaPEF_A__tc3-dkyRvsY5%2B0%3D1Pdmw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB384412A69A943AD1E1AC404ACDB59%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM.
BTH
Reply | Threaded
Open this post in threaded view
|

Re: Needed suggestions for Jenkins Master/Slave architecture

BTH
Hello Jérôme,

Many thanks for your email and very detailed answers! It really helpful 

ในวันที่ อ. 2 ก.พ. 2021 เวลา 21:24 Jérôme Godbout <[hidden email]> เขียนว่า:

Hi, there isn’T much constraint except the setup when moving from master only to master/slave. Only SSH to be setup and here you go. As for the disk space, the workspace is not automatically clean, you might want to clean the working directory before you end your pipeline (after gathering all the wanted information).  This will save space on the slave hard disk. To test your setup, you can use the same machine for you Jenkins slave as the master one, it will work and after you only need to setup additional slave on other machines.

 

Jenkins keep the build information and the project folder will grow over time. You can setup the project to only keep X items or items from a specific length of time. That will reduce the master size.

 

But keep in mind the slave Harddrive will be stressed a lot, they will have a short life time. I backup the master project and have a reliable setup with raid there. Slave are burnable, you don’t really care, fast enough to do the job, died, just put back a new image that kickstart a slave with a new harddrive and up you go.

 

Jérôme Godbout
Software / Firmware Lead

C: (581) 777-0050 
O: (418) 800-1073 ext.: 109  
[hidden email]

dimonoff.com   |    amotus.ca

 

From: [hidden email] <[hidden email]> On Behalf Of banthita limwilai
Sent: February 2, 2021 3:44 AM
To: [hidden email]
Subject: Needed suggestions for Jenkins Master/Slave architecture

 

Hello Folks!

 

I'm about to set up New Jenkins cluster with Master/Slave model. Actually, we already have Jenkins master-only running but it's usually faces run out of memory issue.

 

I've read all the recommended on the official, however there are some details missing there.

 

1. Please suggest for storage for both Master and Slave. Currently our Master-only Jenkins uses huge disk spaces (~200GB) and it tends to increase along with the number of new jobs.

 

My question is where does ./workspace, ./jobs and ./caches (most biggest directories) under $JENKINS_HOME will store? in Master or Slave?

 

2. If I mark Master as drain node (not executing job), so my master can possibly has a minimal resources e.g. CPU 1vCPU and 4GB or less number of memory ?

 

**for my current Master-only Jenkins, we have 30GB memory/200GB

 

3.  If there any issue or concerns from migrating Master-only to Master/Slave ? 

 

Any suggestion would be appreciated :)

 

Cheers,

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEaEQi%2BxfiHndc7%3Dnr3dtjaPEF_A__tc3-dkyRvsY5%2B0%3D1Pdmw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB384412A69A943AD1E1AC404ACDB59%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEaEQiKx%2BmHTXGhR2y30ExFmMg2qBrdREtFFhvduEhH-BxbOsw%40mail.gmail.com.