Worker is terminating.
Worker is Terminating. Are there any configurations that needs to be done before I start using this new Feature ? Also, why is it terminating, I can see that it runs out of memory but is it because of some improper configurations or Injections of services ?
17 Replies
Hi @D_Gamer! How much memory do you have on your worker, it's exactly the same configuration as the server internally, so you'll need a bit more than 2GB to run it at the moment
How do I check that ? Also, where do we have these worker properties configured ?
how are you self-hosting, docker?
This is running locally, on my machine with
yarn start script.okay
what's your OS?
Ubuntu
could you run
free -m ?this is the output
ok so you have a lot
but not that much free that being said
I don't think it's the issue though
is the worker also crashing on main?
I guess so, currently I am merging 0.4.0 with 0.11.0, and this worker feature is new so If it is breaking then I must say it is on main.
okay, let's upgrade you to 0.11 (or even 0.12 first)
Then the worker should be working, there is no reason why it should not
At the moment, you'll need ~2GB to safely run the server and ~1GB for the worker so you should be good
Okay. Got it. I hope it won't break in production through.
what do you mean? Do you also have a production on 0.4 somewhere else?
the worker won't break your existing server. At the moment it's only used for webhooks / messaging jobs
Actually I have already deployed version 0.4 on AWS ECS with Docker. Currently I am merging new features and I need to publish those as well. Of course there are some custom features I have developed myself.
Cool ! Thanks for the explanation man !
Hey @charles, This worker is from Frontend Dev Server. Because frontend dev server keeps crashing.
what do you mean by "frontend dev server"?