<?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: permission denied while using distcp in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/permission-denied-while-using-distcp/m-p/79731#M34443</link>
    <description>The following pattern is the often seen when running DR-like HDFS DistCp&lt;BR /&gt;jobs on secure clusters:&lt;BR /&gt;&lt;BR /&gt;1. Define a HDFS admin group in your user identity backend (lets call it&lt;BR /&gt;'hdfsadmin')&lt;BR /&gt;2. Add qualified (strictly administrative users) users to the new&lt;BR /&gt;'hdfsadmin' group, and ensure all hosts in the cluster show up the new user&lt;BR /&gt;group when running an 'id username' command&lt;BR /&gt;3. On both clusters, alter dfs.permissions.supergroup via HDFS -&lt;BR /&gt;Configuration - "Superuser Group" field in CM to use "hdfsadmin", which&lt;BR /&gt;allows members of this group to act as HDFS superuser (equivalent to 'hdfs'&lt;BR /&gt;user when it comes to filesystem access activities)&lt;BR /&gt;4. Run DistCp as any user who has been allowed membership of 'hdfsadmin'&lt;BR /&gt;group&lt;BR /&gt;</description>
    <pubDate>Wed, 12 Sep 2018 22:46:46 GMT</pubDate>
    <dc:creator>Harsh J</dc:creator>
    <dc:date>2018-09-12T22:46:46Z</dc:date>
  </channel>
</rss>

