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

[question] What are the risks of the "experimental" generate_node_id feature? #203

Open
jwietelmann opened this issue Jun 7, 2021 · 4 comments

Comments

@jwietelmann
Copy link

Seems like generate_node_id is a couple years old now. Is it considered experimental?

We're looking at using Kubernetes autoscaling, so to handle the issue of what happens when we scale down, it's either use generate_node_id or migrate off of verk. I'd like to figure out how safe the feature is at this point.

What should we be watching out for, if anything?

@edgurgel
Copy link
Owner

edgurgel commented Jun 9, 2021

Great question. I think we can safely update this to not be considered experimental anymore. It has been used in production for a few years and it has worked as intended 👌 . It could probably default to true tbh

@he9lin
Copy link

he9lin commented Feb 7, 2024

Does this mean if I have generate_node_id to true, I can safely spin up two dynos on Heroku for my app?

Thanks in advance and thanks for creating verk

@edgurgel
Copy link
Owner

edgurgel commented Feb 7, 2024

Yes! It's the way to go!

@he9lin
Copy link

he9lin commented Feb 7, 2024

That's great! Thanks again!

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

No branches or pull requests

3 participants