.
From: John Sirois <jsir...@apache.org>
Sent: Tuesday, April 19, 2016 19:37
To: Joshua Cohen
Cc: dev@aurora.apache.org
Subject: Re: [PROPOSAL] Switch aurora client from service discovery to HTTP
redirects.
On Mon, Apr 18, 2016 at 4:37 PM, Joshua Cohe
On Mon, Apr 18, 2016 at 4:37 PM, Joshua Cohen wrote:
> And apparently this is not part of our fork at all, the client already
> supports this today! The only potential change that would be required would
> be ensuring the client properly follows redirects.
>
Aha - yes. Thank
And apparently this is not part of our fork at all, the client already
supports this today! The only potential change that would be required would
be ensuring the client properly follows redirects.
On Mon, Apr 18, 2016 at 5:35 PM, Joshua Cohen wrote:
> Er, it's not
Er, it's not `proxy_url`, it's `scheduler_uri` (which makes much more
sense ;)).
On Mon, Apr 18, 2016 at 5:34 PM, Joshua Cohen wrote:
> I'm not opposed to this, in fact we already do something similar
> internally. We've forked clusters.py to allow configuring a `proxy_url`
I'm not opposed to this, in fact we already do something similar
internally. We've forked clusters.py to allow configuring a `proxy_url` for
each cluster. If that's present, then the client will use it rather than
performing service discovery to communicate with the scheduler.
On Mon, Apr 18,
As part of work on switching the Aurora scheduler from using a copy of the
Twitter zookeeper libs to the Apache Curator libs [1], I'd like to enable a
Curator feature (GUID protection [2]) that will make the scheduler more
robust to ZooKeeper outages but has the side-effect of breaking the