GitHub user dosubot[bot] added a comment to the discussion: No cleaning of the 
Celery (RabbitMQ) queue

<!-- Greeting -->
Hi @devmdr! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the 
superset team.

<!-- Answer -->
Superset does not manage Celery or RabbitMQ queue cleanup—this is handled by 
Celery itself and your broker configuration. The messages you see with 
`"status": "SUCCESS"` are likely Celery task result messages, which should be 
managed by the result backend, not left in the broker queue if everything is 
working as expected. Superset's prune tasks only clean up internal database 
logs, not Celery queues or RabbitMQ messages 
([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/tasks/scheduler.py)).

To ensure queues are cleaned regularly, check your Celery settings—especially 
`result_expires` (which controls how long task results are kept in the backend) 
and make sure your workers are running and acknowledging tasks. With RabbitMQ 
and the `rpc://` result backend, Celery should remove result messages after 
they are retrieved, but if clients never fetch results, messages can 
accumulate. You can also use RabbitMQ management tools or Celery's `purge` 
command to manually clear queues if needed.

If you continue to see persistent messages, review your Celery worker logs for 
errors or misconfiguration, and consider setting `result_expires` to a 
reasonable value (for example, `result_expires = 3600` for one hour) in your 
Celery config to help with automatic cleanup.


<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/53aaf3fe-40db-4e83-bd40-0fe56eb2f41e?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
 nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34578)

GitHub link: 
https://github.com/apache/superset/discussions/34578#discussioncomment-14021919

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to