Jake Verbaten

Hyperbahn is not node6 compliant yet. It should work on node0.10 or node4

@sashahilton00 I shared some of our internal docs: - [Hyperbahn overview google](https://docs.google.com/document/d/15QzdFkGS4iWGko9v_h1NUOjED4Pk5bJMgGFf1TVyLf8/edit) - [Hyperbahn overview github](https://github.com/uber/hyperbahn/blob/master/docs/overview.md) > there seem to be several references to Hyperbahn routers, yet little to no...

@sashahilton00 I should also give a warning, the hyperbahn service discovery & routing solution is built by Uber, for Uber. The open source project is poorly documented and running hyperbahn...

Figuring out which serviceNames to enable with this "degraded load balancing" strategy is going to be involved. One strategy is to: - look at top10 workers in terms of average...

:+1: As mentioned it would be nice to get stats into how often a ring change happens and what "damage" or side effect it causes on the hyperbahn network.

@jwolski By damage I meant measuring impact. - Amount of socket thrashing in hyperbahn exit workers - Amount of Declined Error Frames caused to applications. - Increased latency due to...

lgtm. May cause hilarity / confusion.

This seems reasonable. I want to try running it and looking at a diff of the pre-process vs post-process. Also we need to figure out what to do in terms...

tests fail lal.

we need to fix debug logtron.