Racer clustering is incompatible with Nodejitsu #156

Closed
bdefore opened this Issue Oct 20, 2012 · 6 comments

Comments

Projects
None yet
4 participants
@bdefore

bdefore commented Oct 20, 2012

According to Nodejitsu support, Derby is unable to deploy due to it using clustering that conflicts with Nodejitsu's clustering.

@lackac

This comment has been minimized.

Show comment Hide comment
@lackac

lackac Oct 21, 2012

Contributor

Derby is using up for clustering. Several PaaS providers have a problem with this. You could drop using up in order for your app to work with these providers. This thread on Google Groups will be of help: https://groups.google.com/d/msg/derbyjs/y73eqpzXm1g/xFSYzvUTpFIJ

Contributor

lackac commented Oct 21, 2012

Derby is using up for clustering. Several PaaS providers have a problem with this. You could drop using up in order for your app to work with these providers. This thread on Google Groups will be of help: https://groups.google.com/d/msg/derbyjs/y73eqpzXm1g/xFSYzvUTpFIJ

@switz

This comment has been minimized.

Show comment Hide comment
@switz

switz Dec 10, 2012

I'm curious if we could eventually get up to run stably in production (outside of a heroku/nodejitsu). It'd be nice to have built in clustering.

switz commented Dec 10, 2012

I'm curious if we could eventually get up to run stably in production (outside of a heroku/nodejitsu). It'd be nice to have built in clustering.

@lackac

This comment has been minimized.

Show comment Hide comment
@lackac

lackac Dec 10, 2012

Contributor

I'm running http://bibliaolvaso.hu with up in production and it's quite
stable. The only issue I have is an occasional "Model bundling took longer
than 1000 ms" error but I don't think this is related to up.

Contributor

lackac commented Dec 10, 2012

I'm running http://bibliaolvaso.hu with up in production and it's quite
stable. The only issue I have is an occasional "Model bundling took longer
than 1000 ms" error but I don't think this is related to up.

@switz

This comment has been minimized.

Show comment Hide comment
@switz

switz Dec 10, 2012

Hmm, when I was running up in production my site would crash after ~30 hours without fail. Since then, my site has been running smooth. Have you tried increasing the number of workers that up uses? I'm curious if it clusters properly.

On Monday, December 10, 2012 at 4:52 AM, László Bácsi wrote:

I'm running http://bibliaolvaso.hu with up in production and it's quite
stable. The only issue I have is an occasional "Model bundling took longer
than 1000 ms" error but I don't think this is related to up.


Reply to this email directly or view it on GitHub (codeparty#156 (comment)).

switz commented Dec 10, 2012

Hmm, when I was running up in production my site would crash after ~30 hours without fail. Since then, my site has been running smooth. Have you tried increasing the number of workers that up uses? I'm curious if it clusters properly.

On Monday, December 10, 2012 at 4:52 AM, László Bácsi wrote:

I'm running http://bibliaolvaso.hu with up in production and it's quite
stable. The only issue I have is an occasional "Model bundling took longer
than 1000 ms" error but I don't think this is related to up.


Reply to this email directly or view it on GitHub (codeparty#156 (comment)).

@lackac

This comment has been minimized.

Show comment Hide comment
@lackac

lackac Dec 10, 2012

Contributor

Good question. I'll have to check that later. :)

Contributor

lackac commented Dec 10, 2012

Good question. I'll have to check that later. :)

@nateps

This comment has been minimized.

Show comment Hide comment
@nateps

nateps Jun 5, 2013

Contributor

Not relevant in 0.5

Contributor

nateps commented Jun 5, 2013

Not relevant in 0.5

@nateps nateps closed this Jun 5, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment