Assault by GC - Hackdot

Re:Assault by GC by sams99 on Tuesday October 25, 2011 @04:07AM (#3153265)

Really?

We register for notifications from the GC using a magic threshold number that could mean anything.

Then we quickly notify the rest of the webs a GC is pending on our "message bus". They let us know they are safe from GC at the moment. If they are not you are in a pickle.

Then we notify HAProxy that we are about to run a GC and ask it to tell us when it is done draining the current requests and taking our web offline.

Once notified we perform the GC manually

Then we notify HAProxy that we are done with the GC so it can add us back to the pool.

What could possibly go wrong?

[ Parent | on HN ]

Re:Assault by GC by JasonPunyon on Tuesday October 25, 2011 @05:20AM (#3153415)

2 magic threshold numbers that could mean anything :)

[ Parent | on HN ]

Re:Assault by GC by tedunangst on Tuesday October 25, 2011 @11:58AM (#3154505)

Or you could just tell haproxy you're going to be low priority for a little bit and not worry about every single last request never being processed on GCing server.

[ Parent | on HN ]

Re:Assault by GC by sams99 on Wednesday October 26, 2011 @01:49AM (#3157366)

you do realise that only about 0.09% of our requests were affected by this, catching them all is the whole point here.

[ Parent | on HN ]