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.

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

Asynq doesn't listen on any port ! #153

Open
codecoron opened this issue Aug 27, 2024 · 1 comment
Open

Asynq doesn't listen on any port ! #153

codecoron opened this issue Aug 27, 2024 · 1 comment

Comments

@codecoron
Copy link

Hi

In mqueue scheduler and mqueue job which base on asynq doesn't listen on any port. Actually other process enqueue task by redis indircetly.

Should it removed ?

Name: mqueue-scheduler
Host: 0.0.0.0
# Port: 3003
Mode: dev
Name: mqueue-job
Host: 0.0.0.0
# Port: 3002 
Mode: dev

My Test Here

./data/server/mqueue-scheduler -f app/mqueue/cmd/scheduler/etc/mqueue.yaml
【LotteryDrawScheduler】 registered an entry: "91303128-7318-4103-8c3e-afd41aff775b" 
【wishCheckinScheduler】 registered an entry: "443241d0-a083-465c-b0b4-5bd35ade272c" 
asynq: pid=1624910 2024/08/27 02:16:42.839388 INFO: Scheduler starting
asynq: pid=1624910 2024/08/27 02:16:42.839396 INFO: Scheduler timezone is set to Asia/Shanghai
asynq: pid=1624910 2024/08/27 02:16:42.839405 INFO: Send signal TERM or INT to stop the scheduler

No process listen on 3003

# lsof -i:3003
# 
@Mikaelemmmm
Copy link
Owner

Yes, the port is useless. It's like a message queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@codecoron @Mikaelemmmm and others