aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zameer Manji <zma...@apache.org>
Subject Re: Feature proposal: ability to apply a block on all updates in the scheduler
Date Wed, 11 Feb 2015 19:56:46 GMT
+1 to a read only mode.

On Wed, Feb 11, 2015 at 11:54 AM, Maxim Khutornenko <maxim@apache.org>
wrote:

> +1 to the proposal. However, the ticket already exists:
> https://issues.apache.org/jira/browse/AURORA-1091.
>
> On Wed, Feb 11, 2015 at 11:51 AM, David McLaughlin
> <dmclaughlin@apache.org> wrote:
> > Hi aurora-dev,
> >
> > I'd like to propose a feature that I think could be useful to
> > admins/operators of Aurora clusters. The feature would be to allow an
> > administrator of the cluster to "block" write operations from happening
> in
> > the scheduler, essentially putting it into read-only mode for a period of
> > time. It could be a simple global lock across the entire cluster or we
> > could get sophisticated and apply locks across roles, environments or
> > specific jobs.
> >
> > I think this has the potential to be very simple (reject new RPCs but
> allow
> > existing operations to continue) or it can start to get complicated (also
> > pause all in-progress updates and other reschedule events).
> >
> > Would welcome feedback on this idea before I create a ticket.
> >
> >
> > Thanks,
> > David
>
> --
> Zameer Manji
>
>

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