Home > Storage > PowerScale (Isilon) > Industry Solutions and Verticals > Analytics > Dell EMC PowerScale and Cloudera Replication Manager QATS Certification Report and Process > Issues and workaround
Note the following known issues and workarounds:
Solution: CM > Yarn > Configuration > HDFS Replication Advanced Configuration Snippet (Safety Valve) for yarn-site.xml
<property><name>mapreduce.jobhistory.intermediate-done-dir</name><value>/user/history/done_intermediate</value></property>
Solution: Set distcp.copy.diff to false in hdfs_client_config_safety_valve
isi hdfs proxyusers modify hive --zone=System --add-user=root
isi hdfs proxyusers view hive --zone=System
Solution: Add the group name of the user (for example, bdr) who will be used as Run As Username of the replication schedule as “Authorized Admin Group” in target cluster HDFS/PowerScale service's configuration in CM.
Solution: Add a user mapping rule in PowerScale. For example:
Workaround: By default (if the Log Path is not provided under the replication policy in CM), the logs are kept under “/user/<username>/.cm/distcp”; otherwise, “<userProvidedLogPath>/.cm/distcp” is used to keep the logs for distcp jobs. Currently, the user cannot change the default log expiration time (internal Cloudera Jira). Thus, if the space is the constraint, these logs have to be cleaned up manually.