change to prefork, with ADR note in docs - #133
Conversation
|
Warning Review limit reached
Next review available in: 37 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe Celery request-processor worker now runs with the prefork pool instead of eventlet. An ADR documents the decision, explicit concurrency configuration, operational consequences, and future ECS scaling options. ChangesCelery prefork worker pool
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/celery-worker-pool.md`:
- Around line 53-54: Update the concurrency statement in the Celery worker pool
documentation to avoid claiming there is no behavioral change; state only that
configured task concurrency remains 1, while preserving the existing note about
deliberately increasing it via the roadmap.
- Around line 22-27: Revise the Eventlet caveat in the workload discussion to
state that psycopg2 may cooperate when Eventlet greening is enabled, while this
workload’s transforms and database writes may still limit parallelism; avoid
presenting GIL or blocking C-call serialization as inherent. Also qualify any
claim that the 30-minute task_time_limit never fired, tying it to the deployed
Celery/Eventlet version or verified blocking-task evidence.
In `@request-processor/docker-entrypoint.sh`:
- Line 4: Quote the CELERY_WORKER_CONCURRENCY expansion in the Celery worker
command, using the default value of 1 while preserving it as a single argument
to --concurrency.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4fa9e842-98d3-48df-b5a8-1fe8298bb68a
📒 Files selected for processing (2)
docs/celery-worker-pool.mdrequest-processor/docker-entrypoint.sh
What type of PR is this? (check all applicable)
Description
Async tasks were never being killed, an investigation revealed this was due to eventlet being used, this has been changed to prefork with ADR note in docs here for this.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Tested in local with SIGKILL working and tested in Dev.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
No
[optional] Are there any dependencies on other PRs or Work?
No