At the queue level, you've define a certain amount of ressources. For
argument sake, let's say that your queue is allowed to consume 50% of your
cluster and max 100%. As a single user, you won't be able to consume more
than 50%. If you've got two different user within the queue, they would be
able to use 100% of teh overall cluster. You can define how much a user is
entitle to take of the overall Q by playing with yarn.scheduler.
capacity.root.production.user-limit-factor.

If with job1 userA has reached the max he is entitled, he will need to wait
for some slots to become free before job2 start.

Olivier
On 26 November 2013 10:46, ch huang <[EMAIL PROTECTED]> wrote:
  Latest From Our Blog:  SAP HANA + Hadoop: A Perfect Match
<http://hortonworks.com/blog/sap-hana-hadoop-a-perfect-match/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature>

--
CONFIDENTIALITY NOTICE
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