hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@altiscale.com>
Subject Re: "Reservation" ambiguity
Date Mon, 03 Aug 2015 18:20:54 GMT

On Jul 29, 2015, at 10:37 AM, Karthik Kambatla <kasha@cloudera.com> wrote:

> Hi folks
> We use the word "reservation" to mean both (1) reservations on nodes to
> avoid starvation of big container asks, and (2) the recent SLA work. This
> is confusing both to developers and end-users.
> I was wondering if people are open to calling the first one a "hold" and
> the second one a "reservation". We can change the terminology in the code
> and add new metrics for hold in branch-2 and remove the metrics for
> reserved* in Hadoop-3?
> Thoughts?

Whichever one got checked in first gets ‘reservation’.

View raw message