-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Redis Queue for Persistent Task #5371
base: main
Are you sure you want to change the base?
Conversation
f0b6298
to
c3e69df
Compare
Are you still interested in working on this @linznin? It looks like it is partially implemented |
@linznin please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
I have implemented most of the functionality, but I encountered an issue where tasks are not completing properly. I'm currently investigating whether this is due to issues with task reception. However, I haven't had enough time to fully resolve it yet, so I will need more time to complete the implementation. |
Thanks for the update. Once the maintainers team get to work on extending the runtime we will come back to this. |
Why are these changes needed?
This PR introduces Redis as an external storage mechanism for task queuing in Autogen's Distributed Agent Runtime. The existing asyncio.Queue implementation does not persist tasks across service restarts, leading to potential loss of in-progress tasks. By integrating Redis, tasks and agent states can be preserved beyond service restarts, improving reliability and scalability.
Related issue number
Closes #5327
Checks