teamhephy/builder

List of issues with running 2 or more builder pods in a cluster

Open

#39 opened on Mar 21, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (12 forks)auto 404
enhancementhelp wantedproposal

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

From @arschles on January 7, 2016 22:10

This issue tracks the current limitations of builder as a clustered system

  • It uses a filesystem based lockfile to prevent 2 or more git pushes at the same time
    • In a multi-builder setup, this means that multiple git pushes can in fact happen at the same time
    • To solve, the lock will need to be distributed
  • It keeps git repositories on disk and runs pre-receive hooks on them to deploy
    • In a multi-builder setup, this means that one git push may only have to push a few refs, while another identical git push may have to push all refs. Not the end of the world
    • To solve, the refs list will need to be moved off of local disk to a shared location (object storage?)

Copied from original issue: deis/builder#86

Contributor guide

Research direction
Research distributed locking mechanisms (e.g., etcd, Consul) and shared storage for git refs (e.g., S3, object storage) to address the limitations of running multiple builder pods.
Tech stack
go
Domain
backenddistributed systems
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30