Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

working with serverless server #647

Closed
xiaosha007 opened this issue Jul 19, 2021 · 0 comments
Closed

working with serverless server #647

xiaosha007 opened this issue Jul 19, 2021 · 0 comments

Comments

@xiaosha007
Copy link

Hi, I am using a serverless server and implemented bullMQ as job scheduler on it. Each time i deployed a new version to my server, it will create a new server instance. In this situation, I noticed that the old server instance is not killed immediately and thus the worker is still serving with lower processing power. Therefore, there will be two workers serving at the same time, which is not what I desired. Do anyone has issue with this ? I am willing to learn and listen to your advice :D
@taskforcesh taskforcesh locked and limited conversation to collaborators Jul 21, 2021
@manast manast closed this as completed Jul 21, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@manast @xiaosha007