Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR: "org.apache.hadoop.security.AccessControlException: Permission denied" while running mapping in Native execution mode using Informatica BDM
Problem Description

While running mappings involving objects from Kerberized Hive/HDFS services in 'Native'  execution mode, mapping execution fails with permission issue. From the mapping run log, it could be seen that Kerberos user, specified at 'Hadoop Kerberos Service Principal Name'  of DIS was used for failed execution, instead of the user in the Hive/HDFS connections and it led to the failure.

 

Log Trace

 

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] : 2019/04/23 21:25:18.352 [main]: ERROR shellcmd.FileCopyUtil: Error encountered:

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] : org.apache.hadoop.security.AccessControlException: Permission denied: user=ths, access=WRITE, inode="/user/infagcs/tutorial_dept_emp.out":infagcs:hdfs:drwxr-xr-x

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2598)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2533)

2019-04-23 21:25:18.366 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2417)

..

..

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:475)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:416)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:926)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:907)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:803)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:792)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at com.informatica.platform.dtm.executor.hadoop.shellcmd.FileCopyUtil$CopyLocalFileToHdfsTask.call(FileCopyUtil.java:986)

2019-04-23 21:25:18.367 <Thread-177> INFO: [Hive task exec0] :  at com.informatica.platform.dtm.executor.hadoop.shellcmd.FileCopyUtil.run(FileCopyUtil.java:615)

​ 

Cause

Reported issue occurs, when the 'Mapping Impersonation Name' attribute of the mapping was not configured with details of the user, who is having required permissions. 

Solution

While running the mapping in 'Native' execution mode, in case of Kerberized Hadoop cluster environment, it would be required to specify the user, who is having the privileges to perform read/write operation as 'Mapping Impersonation Name'. On doing so, configured user would be used, instead of the user specified at DIS level for the read or write operations in the Hadoop cluster services.  


Perform the following steps to specify the impersonation name for the mapping executed in 'Native' mode, which fails with permission error:

 

  1. Log in to Developer client.
  2. Connect to the MRS, containing the required mapping and then open it.
  3. Navigate to 'Properties > Runtime' section of the mapping.
  4. Under 'Native'  section, there would be an attribute named 'Mapping Impersonation Name'.
  5. Specify the value for the same with the user, who is having the required read/write permissions. It would be required to specify the complete Kerberos 'Service Principal Name' (SPN) of the user (say, infagcs@INFORMATICA.COM), instead of simple user id (say, 'infagcs').

 


bdm_native_mapping_impersonation_username.png 


      6. Once specified, save changes and then re-run the mapping in Native execution mode. 


With the above configurations, mapping execution should be using the impersonation user specified in Mapping level for its operations, instead of the 'Hadoop Kerberos Service Principal Name' configured in DIS.

 


More Information
Applies To
Product: Big Data Management; Data Quality; Big Data Quality
Problem Type: Configuration; Security
User Type: Developer; Administrator
Project Phase: Configure; Onboard; Implement
Product Version: Informatica 10.1.1; HotFix; Informatica 10.2; Informatica 10.2.1; Informatica 10.2.2
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:5/16/2019 6:20 AMID:575291
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)