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

Problem with auto scaling #23

Closed
phw opened this issue Jan 22, 2016 · 2 comments
Closed

Problem with auto scaling #23

phw opened this issue Jan 22, 2016 · 2 comments
Assignees

Comments

@phw
Copy link
Contributor

phw commented Jan 22, 2016

When scaling up an application with this cartridge, the newly instantiated gear will always install the latest node version regardless of the .openshift/NODE_VERSION_URL marker. This is because the gear is first setup and then the content is synced over. So during the setup the $OPENSHIFT_REPO_DIR is still empty.

I don't know yet how to properly solve this. I think the cartridge should check the and update the nodejs version in some other hook, but I have not found any good information what hooks are called in which order for newly setup scaled gears.

But I have a workaround implemented at phw@50469aa . This commit allows the node.js version be specified via the environment variable NODE_VERSION_URL. Since the environment is made available to new gears immediately it will be setup with the correct version.

@icflorescu
Copy link
Owner

I'll merge your workaround if you don't mind :-)

@icflorescu
Copy link
Owner

This appears to be working now, so I'm closing the issue. Thanks a lot!

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

No branches or pull requests

2 participants