stackabletech / stackabletech/airflow-operator
Increase memory limit for git-sync container
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
A user reported that the git-sync containers crashes (OOM) when trying to sync a large repo with dags (>100 MB). We should either increase the memory limit (currently 64 Mi) or make this easier overridable. It's currently possible with podOverrides but they need to be added for both git-sync containers in each component:
...
schedulers:
podOverrides:
spec:
initContainers:
- name: gitsync-0
resources:
limits:
memory: 256Mi
cpu: 100m
requests:
memory: 256Mi
cpu: 200m
containers:
- name: gitsync-1
resources:
limits:
memory: 256Mi
cpu: 100m
requests:
memory: 256Mi
cpu: 200m
celeryExecutors:
podOverrides:
...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the git-sync container resource defaults and the pod specifications for the schedulers and celeryExecutors components. Compare the current 64 Mi limit with the podOverrides example, then verify that large-repository synchronization no longer causes an OOM and that the resource setting is consistently overridable where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100