GitLab Runner and Rails API Concurrent Job Priority

GitLab Runner and Rails API: Job Priority Logic During Concurrent Polling

0 reputation · 18 May 2023, 15:18 UTC

46K views0

GitLab Runners utilize a polling mechanism to request available jobs from the GitLab Rails API. While concurrency is manageable via the concurrent setting in config.toml and the global instance limits, the interaction between multiple runners and the server-side job queue introduces complexity during high-volume bursts.

When numerous runners with overlapping tags poll the API simultaneously, the server must determine which runner receives which pending job. There is uncertainty regarding the internal priority queuing logic when runners with different tag sets compete for the same pool of pending jobs under extreme concurrency.

Does the GitLab Rails API prioritize runners with more specific tag matches over those with broader matches during a single polling cycle?
How is the job distribution handled when multiple runners request work at the exact same millisecond?

Keep exploring this topic

GitLab CI job image drift symptom: tag pinning vs digest pinning across runners

GitLab CI/CD pipelines can drift across runners when job images use mutable tags and include refs point to branches. Digest and SHA pinning help, but pull_policy, caches, and runner version differences complicate the choice.

GitLab CI/CD masked variable coverage for Base64-encoded job output

GitLab CI/CD masked variables use exact string replacement in job logs. When a secret is transformed into Base64 during execution, the encoded output may appear unmasked. Is there a configuration to mask derived representations, or is exact-match replacement the only supported behavior?

Docker : exec /usr/bin/sh: exec format error

I created a custom docker image and push it to docker hub but when I run it in CI/CD it gives me this error. exec /usr/bin/sh: exec format error Where : Dockerfile FROM ubuntu:20.04 RUN apt-get update RUN apt-get install -y software-properties-common RUN apt-get install -y python3-pip RUN pip3 install robotframework .gitlab-ci.yml robot-f

Cannot connect to the Docker daemon at tcp://localhost:2375/. Is the docker daemon running. On GitLab

I'm trying to build the CI pipeline in GitLab. I'd like to ask about making the docker work in GitLab CI. From this issue: https://gitlab.com/gitlab-org/gitlab-runner/issues/4501#note_195033385 I'm follow the instruction for both ways. With TLS and not used TLS. But It's still stuck. Which in same error Cannot connect to the Docker daemon

GitLab Runner and Rails API: Job Priority Logic During Concurrent Polling

0 answers

Your perspective belongs here.

0 question comments

Good answers start here.