Rails Spawn plugin under nginx

Server NGINX
1

Howdy folks -
I am having trouble with the ‘Spawn’ plugin, which is used to launch
long-running processes in the background.

When I hit a single mongrel process, it works great. However, when I hit
it through nginx, a the long-running task stays within the same process.
I have no clue why this is happening, but it is dragging down my
performance.

Does anyone have any input?

Thanks!

2

Hey,

Every client we have using spawn at engine yard has problems. The
short answer is just don’t do it. You need to use real queueing a la
bj, backgroundrb, starling, etc. I’m pretty sure that the upstream
gets confused with all the fd closing/reopening/reconnecting.

__
Corey D.
[email protected]
(866) 518-9273 x207

3

Howdy Corey-
Thanks for your input. I will look into one of these alternatives.

Again, thanks for the quick response!

Corey D. wrote:

Hey,

Every client we have using spawn at engine yard has problems. The
short answer is just don’t do it. You need to use real queueing a la
bj, backgroundrb, starling, etc. I’m pretty sure that the upstream
gets confused with all the fd closing/reopening/reconnecting.

__
Corey D.
[email protected]
(866) 518-9273 x207

4

BTW, the problems with Nginx were solved shortly after these messages
appeared. The solution was to have spawn disconnect from the listening
sockets in the child process. You should be able to use Spawn with
nginx without problems now.

Tr Schneit wrote:

Howdy Corey-
Thanks for your input. I will look into one of these alternatives.

Again, thanks for the quick response!

Corey D. wrote:

Hey,

Every client we have using spawn at engine yard has problems. The
short answer is just don’t do it. You need to use real queueing a la
bj, backgroundrb, starling, etc. I’m pretty sure that the upstream
gets confused with all the fd closing/reopening/reconnecting.

__
Corey D.
[email protected]
(866) 518-9273 x207