search

RichardKnop / machinery

Machinery is an asynchronous task queue/job queue based on distributed message passing.
Mozilla Public License 2.0
7.56k stars 917 forks source link

Debugging with goland, the task queue reports an error #756

Open jeefs opened 2 years ago

jeefs commented 2 years ago

WARNING: 2022/04/24 16:45:55 worker.go:101 Signal received: interrupt WARNING: 2022/04/24 16:45:55 worker.go:106 Waiting for running tasks to finish before shutting down 2022/04/24 16:45:55 INFO logger/logger.go:76 Shutdown Server ... WARNING: 2022/04/24 16:45:55 broker.go:118 Stop channel 2022/04/24 16:45:55 INFO logger/logger.go:76 Server exiting

ingfdoaguirre commented 2 years ago

Hi you need to give us more information about your problem, like some of your code, settings, etc.

The problem you are posting, is not really an error, is just when the script receives a TERM signal (Typically ctrl + c) and the script is gracefully terminating.

jeefs commented 2 years ago

I use redis as a broker, the worker runs in a separate concurrent thread, I use goland single point debugging, when clicking next the debug exits，

My configuration is as follows: machinery: broker: "redis://127.0.0.1:6379" default_queue: "default" result_backend: "redis://127.0.0.1:6379" redis: max_idle: 3 max_active: 3 max_idle_timeout: 240 wait: true read_timeout: 15 write_timeout: 15 connect_timeout: 15 normal_tasks_poll_period: 1000 delayed_tasks_poll_period: 500 delayed_tasks_key: "mike"

jeefs commented 2 years ago

After switching to the goland version, the problem disappeared