Closed charneykaye closed 7 years ago
The name of the worker matches the Resque worker naming scheme defined here: https://github.com/resque/resque/blob/e0f850f087160362cec1ae3759c7c1e1d9190381/lib/resque/worker.rb#L777
You can subclass WorkerImpl and override the createName()
method to modify the default behavior if that's easier than modifying the environment.
Thanks for the tip @gresrun -- the environment update seemed best overall, and Jesque has been working very well.
This issue did not appear in our (theoretically at parity with production) Docker-compose setup during local development and integration testing.
However, when deployed to Amazon EC2 via Elastic Beanstalk, this exception is thrown, and there appears to be no way to manually configure Jesque to avoid the issue.
We are currently addressing this at the production deployment configuration layer, because the issue is immediately resolved by adding
127.0.0.1 ip-#-#-#-#
to the/etc/hosts
file (where #.#.#.# is the IP of the current machine).However, I am curious why Resque is hard-coded to require this for the simple
createName()
function while instantiating a worker.