Ah, that's what I was looking for. Thanks! On Wed, Feb 11, 2015 at 11:54 AM, Maxim Khutornenko <ma...@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 > <dmclaugh...@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 >
