Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing node options to slc run #56

Open
KidkArolis opened this issue Sep 6, 2014 · 9 comments
Open

Passing node options to slc run #56

KidkArolis opened this issue Sep 6, 2014 · 9 comments
Assignees
Labels

Comments

@KidkArolis
Copy link

@KidkArolis KidkArolis commented Sep 6, 2014

Is that possible?

@rmg
Copy link
Member

@rmg rmg commented Sep 7, 2014

There's no nice way to set it directly, but if you specify the full path to strong-supervisor and run it directly like node --harmony /usr/local/bin/sl-run . it should allow you to specify the node flags you want (and more importantly, preserve them in the cluster worker processes).

Does that help?

@sam-github sam-github added #review #sprint54 and removed #review labels Sep 22, 2014
@sam-github sam-github self-assigned this Sep 23, 2014
@sam-github sam-github removed the #sprint54 label Sep 23, 2014
@sam-github sam-github added #sprint59 and removed #community labels Nov 18, 2014
@sam-github sam-github changed the title Running node with --harmony flag Passing node options to slc run Nov 18, 2014
@chandadharap chandadharap added #community and removed #sprint59 labels Nov 24, 2014
@XinV
Copy link

@XinV XinV commented Dec 8, 2015

Any update on this? ideally we like to run slc run --cluster=4 --max_old_space_size=1024

@sam-github
Copy link
Contributor

@sam-github sam-github commented Dec 23, 2015

Did you try @rmg's suggestion above?

@wprater
Copy link

@wprater wprater commented Apr 15, 2016

There's no nice way to set it directly, but if you specify the full path to strong-supervisor and run it directly like node --harmony /usr/local/bin/sl-run . it should allow you to specify the node flags you want (and more importantly, preserve them in the cluster worker processes).

sl-run is no longer a script in strongloop? will the same example work as expected with slc

node --max_old_space_size=300 /usr/local/bin/slc start

edit:
looks like the scripts are in
/usr/local/lib/node_modules/strongloop/node_modules/.bin/

so, theoretically this should work, but will it use the same node process to spawn new workers?
node --max_old_space_size=450 /usr/local/lib/node_modules/strongloop/node_modules/.bin/sl-start

@sam-github
Copy link
Contributor

@sam-github sam-github commented Apr 25, 2016

Probably won't work through the two extra layers, there (sl-start and sl-pm), sorry.

@paperrr1
Copy link

@paperrr1 paperrr1 commented Jul 29, 2016

any solution to this??

@nkgupta1989
Copy link

@nkgupta1989 nkgupta1989 commented Jan 31, 2017

Bumping this thread again,
Below thing is not working
/opt/node/bin/node --max_old_space_size=3072 /opt/node/lib/node_modules/strong-pm/bin/sl-pm.js

Can some one help with Passing node options to slc run

@sam-github
Copy link
Contributor

@sam-github sam-github commented Jan 31, 2017

There isn't a solution for this now, other than to use sl-run directly. I'm looking at other approaches.

@paperrr1
Copy link

@paperrr1 paperrr1 commented Mar 10, 2017

Any update? This has been an issue for 3 years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.