Skip to content
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.

Sign up for GitHub

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

Jump to bottom

command_queue has too many unacked messages #47

Open
EverettSummer opened this issue Jul 6, 2023 · 1 comment
Open

command_queue has too many unacked messages #47

EverettSummer opened this issue Jul 6, 2023 · 1 comment

Comments

@EverettSummer
Copy link
Member

It looks like both JobScheduler and JobExectuor use prefetch = true to receive commands from the same queue while the exchange is a 'direct' exchange. If the JobExecutor is busy, the command may not be responded.
@EverettSummer
Copy link
Member Author

The unacked message is usually a cancel message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@EverettSummer