Hi,
Using HDP 2.0.6, Yarn 2.1
I am trying to access the REST api per the documentation here:
http://hadoop.apache.org/docs/r2.3.0/hadoop-yarn/hadoop-yarn-site/MapredAppMasterRest.html
When I try to access this
http://rm host:8088/ws/v1/cluster/app/application_1401899005478_2241
I get
This is actually the link I was following:
http://hadoop.apache.org/docs/r2.3.0/hadoop-yarn/hadoop-yarn-site/WebServicesIntro.html
On Thu, Jul 3, 2014 at 4:12 PM, Alex Nastetsky anastet...@spryinc.com
wrote:
Hi,
Using HDP 2.0.6, Yarn 2.1
I am trying to access the REST api per
Juan,
What kind of information are you looking for? The service level ACLs are
for limiting which services can communicate under certain protocols, by
username or user group.
Perhaps you are looking for client level ACL, something like the MapReduce
ACLs?
-site.xml and later added the parameter
yarn.scheduler.capacity.root.test1.acl_submit_applications with value
jcfernandez . If I submit a job to queue test1 with user hadoop, it
allows it to run it.
Which is my error?
2014-02-20 16:41 GMT+01:00 Alex Nastetsky anastet...@spryinc.com:
Juan,
What
Please help me understand how capacity and maximum-capacity on a queue
work in the Capacity Scheduler.
My understanding is that a queue is allocated capacity amount of
resources, and if it needs more, it can stretch up to maximum-capacity
resources.
But if that's the case, why do we need
Thanks, makes sense now.
On Feb 19, 2014 9:35 PM, Jian He j...@hortonworks.com wrote:
Yes, in the scenario you mentioned, the scheduler will take away the 10%
from queue B and give it back to queue A
On Wed, Feb 19, 2014 at 5:35 PM, Alex Nastetsky anastet...@spryinc.comwrote:
Thanks Jian
Hi,
I am trying to secure multiple MR job queues from being accessed from
unauthorized users.
I know there is acl_submit_applications and acl_administer_queue for a
specific queue, but neither of those properties control who can view the
list of jobs that have been or are executing in a specific
