-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
Centos 7.1.1503, Jenkins 1.620, Docker plugin 0.10.0, Docker 1.7.1
We have 2 Docker hosts configured as Docker Clouds in our master Jenkins box, mainly for load balancing and failover of jobs. We are using "Keep this slave on-line as much as possible" availability setting. Both hosts are set up with exactly the same set of Docker images/containers/labels and are restricted to run a single instance of each container.
To start from scratch and for testing purposes, I deleted all slaves from the Jenkins master. Next, when I launch number of jobs restricted to run on particular label (which is available on both hosts), the Docker container for the corresponding label only starts on one of the hosts and the jobs are then queued up and run in serial on this single slave.
The expected behaviour would be to spin up as much as possible Docker containers (within set limits) and run the queued jobs in parallel on multiple slaves.
Please let me know if you need any further information from me.
[JENKINS-29497] Multiple Docker Clouds - only 1 container starts up when jobs are queueing
| Description |
Original:
We have 2 Docker hosts configured as Docker Clouds in our master Jenkins box, mainly for load balancing and failover of jobs. We are using "Keep this slave on-line as much as possible" availability setting. Both hosts are set up with exactly the same set of Docker images/containers/labels and are restricted to run a single instance of each container. I deleted all Jenkins slaves to start from scratch for testing purposes and when I launch number of jobs restricted to run on particular label (which is available on both hosts), the Docker container only starts on one of the hosts and the jobs are then queued up and run in serial on this single slave. The expected behaviour would be to spin up as much as possible Docker containers (within set limits) and run the jobs in parallel on multiple slaves. Please let me know if you need any further information from me. |
New:
We have 2 Docker hosts configured as Docker Clouds in our master Jenkins box, mainly for load balancing and failover of jobs. We are using "Keep this slave on-line as much as possible" availability setting. Both hosts are set up with exactly the same set of Docker images/containers/labels and are restricted to run a single instance of each container. To start from scratch and for testing purposes, I deleted all slaves from the Jenkins master. Next, when I launch number of jobs restricted to run on particular label (which is available on both hosts), the Docker container for the corresponding label only starts on one of the hosts and the jobs are then queued up and run in serial on this single slave. The expected behaviour would be to spin up as much as possible Docker containers (within set limits) and run the queued jobs in parallel on multiple slaves. Please let me know if you need any further information from me. |
| Summary | Original: Multiple Docker Clouds - Problem with queueing jobs | New: Multiple Docker Clouds - only 1 container starts up when jobs are queueing |
| Assignee | Original: Kanstantsin Shautsou [ integer ] | New: magnayn [ magnayn ] |
| Workflow | Original: JNJira [ 164374 ] | New: JNJira + In-Review [ 181602 ] |
| Assignee | Original: magnayn [ magnayn ] | New: Nicolas De Loof [ ndeloof ] |
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |