hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karthik Kambatla <ka...@cloudera.com>
Subject "Reservation" ambiguity
Date Wed, 29 Jul 2015 17:37:54 GMT
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?

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