Does this work for long-lived connections? Say I've got 1000 TCP connections open to my backend workers and I want to roll out new workers. Will the old connections die or survive the config change?
Stripe open-sources Einhorn
11–20 of 35 posts
Re: Stripe open-sources Einhorn
#12Does this work for long-lived connections? Say I've got 1000 TCP connections open to my backend workers and I want to roll out new workers. Will the old connections die or survive the config change?
Yep, it will indeed work. New workers will be spun up, the old workers will get a signal asking for a graceful restart, and those old workers can hang around for as long as they need. You'll have twice as many workers alive as you might like, but there's not much Einhorn can do about that.
Re: Stripe open-sources Einhorn
#13I just heard of Unicorn / Rainbow as a way to get more out of Heroku workers/dynos. I wonder if this is also compatible, or a better alternative?
I'm new to this whole concept, so am just about to get my feet wet.
Hopefully, Heroku will implement something like this internally, as it seems it would help them to eliminate the greatest flaw with their system - that each deployment require 5-10 seconds of downtime as new dynos are started.
Re: Stripe open-sources Einhorn
#14(The following is off-topic:) I noticed that the Stripe blog doesn't allow comments. I think most people find it odd or frustrating when they can't add their 2 cents to something (for better or for worse!). Any idea which things might have driven this decision? - Not wanting to deal with how most people act on the net? (Or maybe they're in a highly competitive space where the juggernauts wouldn't think twice about tr…
I made the same decision on my personal blog. When there are comments both on a blog and here on HN, the conversation feels unnaturally fragmented to me. Further, when I did have both, comments that self-selected the blog (vs HN) are - in my opinion - much more likely to be spam/promotional, or generally less 'valuable' (e.g. more likely to be simple questions that are already answered in the post).
There's an angle I hadn't considered. The spammy and promotional type of comments would be far more likely to appear directly on the blog since that's where the value (for the commenter) is in leaving them. That's something that moderated comments would control, but you can't moderate your way out of fragmentation.
I would expect more negative comments to be left directly on the blog as well since the commenter won't have to deal with the potential backlash from their community. Which is probably also a good reason to never allow any kind of anonymous of guest comments. (Although that wouldn't stop the truly motivated negative commenters.)
Re: Stripe open-sources Einhorn
#15I'm interested to see some more posts about Einhorn. I would like to see some example use cases for it. Looks like a very interesting project.
Re: Stripe open-sources Einhorn
#16i'm going to fork Einhorn and call it Finkle.
Re: Stripe open-sources Einhorn
#17Am I to understand that Einhorn doesn't require the use of Unix sockets to delegate work to workers? If so, it could work quite nicely for JRuby apps as Java doesn't support Unix sockets and it's therefore not possible to just plop nginx in front of the Web server (Tomcat or Jetty) instances and have it queue up requests to a shared Unix socket like the typical Unicorn setup does.
Re: Stripe open-sources Einhorn
#18Am I to understand that Einhorn doesn't require the use of Unix sockets to delegate work to workers? If so, it could work quite nicely for JRuby apps as Java doesn't support Unix sockets and it's therefore not possible to just plop nginx in front of the Web server (Tomcat or Jetty) instances and have it queue up requests to a shared Unix socket like the typical Unicorn setup does.
That's correct. In fact, at the moment Einhorn only supports TCP sockets. (That being said, I might be mistaken, but I think that Unicorn can also bind TCP sockets.)
Re: Stripe open-sources Einhorn
#19i'm going to fork Einhorn and call it Finkle.
Finkle and Einhorn... Einhorn and Finkle... Finkle is Einhorn... Einhorn is Finkle...
Re: Stripe open-sources Einhorn
#20(The following is off-topic:) I noticed that the Stripe blog doesn't allow comments. I think most people find it odd or frustrating when they can't add their 2 cents to something (for better or for worse!). Any idea which things might have driven this decision? - Not wanting to deal with how most people act on the net? (Or maybe they're in a highly competitive space where the juggernauts wouldn't think twice about tr…
I made the same decision on my personal blog. When there are comments both on a blog and here on HN, the conversation feels unnaturally fragmented to me. Further, when I did have both, comments that self-selected the blog (vs HN) are - in my opinion - much more likely to be spam/promotional, or generally less 'valuable' (e.g. more likely to be simple questions that are already answered in the post).
Makes sense. Then maybe it would be a good idea to link to the HN discussion at the end of each article?