Mathew Heard

all the options that are on round robin shouldnt be that hard as jdomain extends round robin. @holstvoogd Could you please explain your proxy_next_upstream comment? From my understanding that should...

@nicholaschiasson By the way do you have any data on this module and how it interacts with other balancers (e.g least_conn)? What might be required to make jdomain compatible with...

In the situation: ``` upstream upstream_test { server 127.0.0.2; least_conn; jdomain example.com; } ``` Assuming example.com expands to 4 servers how does least_conn behave? 5 total hosts each balanced for...

I too think this would be really good as it would prevent the inrush of DNS queries after daemon reload. Any chance @nicholaschiasson that you are going to look into...

I would be happy to make some contributions on other matters however, like getting the tests working again

We ran into this. Worked around it with a local dns cache. Doesnt help on first server start, but subsequent reloads (which were the problem) are significantly improved. Doesnt help...

In some cases the current method is actually ideal as it doesnt require locks or shared memory (or work per worker for low frequency blocks).

Can confirm same situation with Oracle JRE. :(

Just so you know the hunks Hunk #1 FAILED at 10. Hunk #2 succeeded at 23 (offset 2 lines). Hunk #3 succeeded at 54 (offset 2 lines). Hunk #4 succeeded...

Yeah multiple error log directives are now supported, I can see how this might require more major changes. Take your time and get it right :)