gitcoinco / gitcoinco/web

Segment celery queues

Open
#10,736 0 comments 0 reactions 0 assignees View on GitHub
GR15
Dominant language
JavaScript
Stars
1.8k
Forks
776
PR merge metrics
No merged PRs in 30d

Description

**Overview**
Right now all celery jobs go into the same default queue, which makes it hard to set thresholds or troubleshoot when the queues get too large. We want to segment jobs into more informed / targeted queues to give us more control over the situation.

**Acceptance Criteria**
- Identify relevant segments and categorize celery jobs into new named queues

**XD Links:**

**Tech Details:**
- Some suggested segments are donations + CLR calcs (high-use jobs)

**Open Questions:**

**Notes/Assumptions:**

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are specified. Start by locating the existing Celery job and default-queue configuration, then inventory the jobs and define meaningful queue segments, including donations and CLR calculations; done means relevant jobs are categorized into named queues.

Written by the indexing model from the issue text.

Assessment

Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.