mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #78] [BUG] kill -TERM pid the process still exists #1035
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#1035
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cielu on GitHub (Feb 11, 2020).
Original GitHub issue: https://github.com/hibiken/asynq/issues/78
Originally assigned to: @hibiken on GitHub.
mac os .
I don't know if this is a bug .
The process could only kill by kill -9
@hibiken commented on GitHub (Feb 11, 2020):
@cielu Did you manage to resolve the issue?
You probably need to build the binary first instead of using
go run.@cielu commented on GitHub (Feb 12, 2020):
@hibiken Thank you ! I have resolve the issue .
I know the reason about can't kill that process .
Asynq have own graceful shut down way , but the Gin framework don't
asynq :
so , if I want them work together , Gin should graceful shut down too (receive the signal to exit).
But it is still recommend to separate the asynq workers
@hibiken commented on GitHub (Feb 12, 2020):
Glad that you were able to resolve the issue.
Yes, intended use case for Asynq is to have its own worker binary separate from web server binary.
This was a useful feedback, maybe I can export
StartandStopmethods for theBackgroundto let the user of the library manually handle shutdown. I'll consider that if more users request it.Thanks for creating the issues!
@cielu commented on GitHub (Feb 12, 2020):
Haha,Look forward to version 1.0