y 7 July 2016 at 01:13
>> > *To: *Martin Hrabovčin <martin.hrabov...@gmail.com>
>> > *Cc: *"dev@aurora.apache.org" <dev@aurora.apache.org>, Jake Farrell <
>> > jfarr...@apache.org>, "u...@aurora.apache.org" <u...@aurora.apache.org&
.org" <u...@aurora.apache.org>, "
> > jsir...@apache.org" <jsir...@apache.org>
> > *Date: *Thursday 7 July 2016 at 01:13
> > *To: *Martin Hrabovčin <martin.hrabov...@gmail.com>
> > *Cc: *"dev@aurora.apache.org" <dev@aurora.apache.or
che.org>, "u...@aurora.apache.org" <u...@aurora.apache.org>
> *Subject: *Re: [FEEDBACK] Transitioning Aurora leader election to Apache
> Curator (`-zk_use_curator`)
>
>
>
> Now that 0.15.0 has been released, I thought I'd check in on any progress
> folks
,
"jsir...@apache.org" <jsir...@apache.org>
Date: Thursday 7 July 2016 at 01:13
To: Martin Hrabovčin <martin.hrabov...@gmail.com>
Cc: "dev@aurora.apache.org" <dev@aurora.apache.org>, Jake Farrell
<jfarr...@apache.org>, "u...@aurora.apache.org"
Now that 0.15.0 has been released, I thought I'd check in on any progress
folks have made with testing/deploying the 0.14.0+ with the Aurora
Scheduler `-zk_use_curator` flag in-place.
There has been 1 fix that will go out in the 0.16.0 release to reduce
logger noise on shutdown [1][2] but I have
+1, will enable on our test clusters to help verify
-Jake
On Tue, Jun 14, 2016 at 7:43 PM, John Sirois wrote:
> I'd like to move forward with
> https://issues.apache.org/jira/browse/AURORA-1669 asap; ie: removing
> legacy
> (Twitter) commons zookeeper libraries used for
>
> Assuming we don't run into any roadblocks: How about changing the
> default of `-zk_use_curator` from False to True for the next release?
+1
I believe that was the plan of action, though i can't recall if it was
recorded anywhere more official than the dev list.
On Wed, Jun 15, 2016 at
On Wed, Jun 15, 2016 at 10:49 AM, Bill Farner wrote:
> >
> > Assuming we don't run into any roadblocks: How about changing the
> > default of `-zk_use_curator` from False to True for the next release?
>
>
> +1
>
> I believe that was the plan of action, though i can't recall
Thanks for doing the follow-up! I'll gradually enable the option on our
clusters sometime next week and let you know if we hit any issues.
Assuming we don't run into any roadblocks: How about changing the
default of `-zk_use_curator` from False to True for the next release?
Then we cane make