You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a node.js app running on AWS with Firebase Queue listening to our firebase. At times we want to debug some things or develop new features and it's easier to run the node app locally to see log statements
Is there any way to guarantee that tasks being sent to a queue will be handled by the local process of the running servers without killing the process on the servers? It would also be ok to completely re-route all queues to the local instance if doing just single queues isn't possible.
The text was updated successfully, but these errors were encountered:
There's nothing that's built-in to the queue to do this. I'm not sure in your situation if you have access to the client code, but if you do you could always change the _state value for new items on the queue - then the prod workers wouldn't pick up the new tasks and your local instance could.
If you don't have access to change the client code then I'm not sure of a solution that doesn't involve disabling the deployed workers
We have a node.js app running on AWS with Firebase Queue listening to our firebase. At times we want to debug some things or develop new features and it's easier to run the node app locally to see log statements
Is there any way to guarantee that tasks being sent to a queue will be handled by the local process of the running servers without killing the process on the servers? It would also be ok to completely re-route all queues to the local instance if doing just single queues isn't possible.
The text was updated successfully, but these errors were encountered: