aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin HrabovĨin <martin.hrabov...@gmail.com>
Subject Re: [FEEDBACK] Transitioning Aurora leader election to Apache Curator (`-zk_use_curator`)
Date Thu, 16 Jun 2016 06:03:43 GMT
How should be this flag rolled to existing running cluster? Can it be done
using rolling update instance by instance or we need to stop the whole
cluster and then bring all nodes with new flag?

2016-06-16 5:03 GMT+02:00 Jake Farrell <jfarrell@apache.org>:

> +1, will enable on our test clusters to help verify
>
> -Jake
>
> On Tue, Jun 14, 2016 at 7:43 PM, John Sirois <jsirois@apache.org> 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 Aurora leader election in
> > favor of Apache Curator libraries. The change submitted in
> > https://reviews.apache.org/r/46286/ is now live in Aurora 0.14.0 and
> > Apache
> > Curator based service discovery can be enabled with the Aurora scheduler
> > flag `-zk_use_curator`.  I'd like feedback from users who enable this
> > option.  If you have a test cluster where you can enable
> `-zk_use_curator`
> > and exercise leader failure and failover, I'd be grateful. If you have
> > moved to using this option in production with demonstrable improvements
> or
> > even maintenance of status quo, I'd also be grateful for this news. If
> > you've found regressions or new bugs, I'd love to know about those as
> well.
> >
> > Thanks in advance to all those who find time to test this out on real
> > systems!
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message