[Negitivefrags]

"The first root cause is related to the streaming data API which connects the dyno manifold to the routing mesh. On the dyno management side, an engineer was performing a manual garbage collection process which created an unusual record in the data stream. On the routing side, a bug in the subprocess of the router which processes the incoming stream saw the record as garbage."

This is techno-babble on a scale the world has never seen!

[enneff]

The only unusual terms in that paragraph are "dyno manifold" and "routing mesh", both of which are Heroku-specific technologies that Heroku users should know of. The rest is just normal systems stuff.

[tedunangst]

I can understand the words individually, but I've never before seen or heard of a manual garbage collection process creating an unusual record in a data stream. It's like a tech jargon ad lib.

[cabinguy]

I like the part where some guy/gal with a stop watch was keeping records of every minute.

[joeyh]

Their interactive engineer mesh stream handles this time keeping.

(That is, probably an irc channel..)