<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: YARN with ACL - unable to view logs from RM webconsole in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/YARN-with-ACL-unable-to-view-logs-from-RM-webconsole/m-p/43279#M36063</link>
    <description>&lt;P&gt;If you are referring to MapReduce Job History Server by JH, JHS has its own job ACL control. If a MR job is configured with&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;mapreduce.job.acl-view-job = {users you want to allow to view the job, see mapred-default.xml for details on format}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;Then JHS will allow the specified user to view the job.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jul 2016 16:44:43 GMT</pubDate>
    <dc:creator>haibochen</dc:creator>
    <dc:date>2016-07-27T16:44:43Z</dc:date>
    <item>
      <title>YARN with ACL - unable to view logs from RM webconsole</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/YARN-with-ACL-unable-to-view-logs-from-RM-webconsole/m-p/43268#M36062</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently experimenting with ACLs on YARN pools.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our goal is to have:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;a pool for each application where only the authorized user can submit jobs&lt;/LI&gt;&lt;LI&gt;a group of users for each pool that can view application history and logs&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using the following fair-scheduler.xml file (generated with Cloudera Manager):&lt;/P&gt;&lt;PRE&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&amp;gt;
&amp;lt;allocations&amp;gt;
    &amp;lt;queue name="root"&amp;gt;
        &amp;lt;weight&amp;gt;1.0&amp;lt;/weight&amp;gt;
        &amp;lt;schedulingPolicy&amp;gt;drf&amp;lt;/schedulingPolicy&amp;gt;
        &amp;lt;aclSubmitApps&amp;gt;&amp;lt;/aclSubmitApps&amp;gt;
        &amp;lt;aclAdministerApps&amp;gt;&amp;lt;/aclAdministerApps&amp;gt;
        &amp;lt;queue name="appA"&amp;gt;
            &amp;lt;weight&amp;gt;1.0&amp;lt;/weight&amp;gt;
            &amp;lt;schedulingPolicy&amp;gt;drf&amp;lt;/schedulingPolicy&amp;gt;
            &amp;lt;aclSubmitApps&amp;gt;appA developersA&amp;lt;/aclSubmitApps&amp;gt;
            &amp;lt;aclAdministerApps&amp;gt;appA developersA&amp;lt;/aclAdministerApps&amp;gt;
        &amp;lt;/queue&amp;gt;
        &amp;lt;queue name="appB"&amp;gt;
            &amp;lt;weight&amp;gt;1.0&amp;lt;/weight&amp;gt;
            &amp;lt;schedulingPolicy&amp;gt;drf&amp;lt;/schedulingPolicy&amp;gt;
            &amp;lt;aclSubmitApps&amp;gt;appB developersB&amp;lt;/aclSubmitApps&amp;gt;
            &amp;lt;aclAdministerApps&amp;gt;appB developersB&amp;lt;/aclAdministerApps&amp;gt;
        &amp;lt;/queue&amp;gt;
    &amp;lt;/queue&amp;gt;
&amp;lt;/allocations&amp;gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the point 1. (pool access only by app user) everything works fine, but I can't get to find a working configuration for point 2: for example if user devA (in group developersA) tries to view the logs for an application launched in appA get always the following error (in JH web console):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;User [devA] is not authorized to view the logs for container_1469609032080_0001_01_000001 in log file&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion? Is this the intended behaviour or am I missing something?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our cluster specs/settings:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;yarn.acl.enable = true&lt;/LI&gt;&lt;LI&gt;yarn.admin.acl = "yarn clusterAdminGroup"&lt;/LI&gt;&lt;LI&gt;CDH 5.7&lt;/LI&gt;&lt;LI&gt;Kerberos authentication&lt;/LI&gt;&lt;LI&gt;YARN web interface also using Kerberos authentication&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;Bye&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 10:31:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/YARN-with-ACL-unable-to-view-logs-from-RM-webconsole/m-p/43268#M36062</guid>
      <dc:creator>parnigot</dc:creator>
      <dc:date>2022-09-16T10:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: YARN with ACL - unable to view logs from RM webconsole</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/YARN-with-ACL-unable-to-view-logs-from-RM-webconsole/m-p/43279#M36063</link>
      <description>&lt;P&gt;If you are referring to MapReduce Job History Server by JH, JHS has its own job ACL control. If a MR job is configured with&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;mapreduce.job.acl-view-job = {users you want to allow to view the job, see mapred-default.xml for details on format}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;Then JHS will allow the specified user to view the job.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 16:44:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/YARN-with-ACL-unable-to-view-logs-from-RM-webconsole/m-p/43279#M36063</guid>
      <dc:creator>haibochen</dc:creator>
      <dc:date>2016-07-27T16:44:43Z</dc:date>
    </item>
  </channel>
</rss>

