Apologies for the late reply.

The concept of reservation is used to prevent starvation.

For e.g. let's say you have 2 machines with 8G each. Now each of those are running containers which take up 6G on nodeA and 7G on nodeB.

Another application comes in and then asks for a single container of 4G, which can't be allocated anywhere in the cluster. In this case (e.g.) 4G is reserved on nodeA and is given to the app only when it's available… else, this application would be 'starved' if other apps came in and asked for 1G or 2G and would hence, 4G would never be freed up.

Hope that helps.


On Feb 7, 2014, at 7:58 AM, ricky l <[EMAIL PROTECTED]> wrote:
Arun C. Murthy
Hortonworks Inc.

NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB