Arpit Gupta created FALCON-389:
----------------------------------
Summary: Submit Hcat export workflow to oozie on source cluster
rather than to oozie on destination cluster
Key: FALCON-389
URL: https://issues.apache.org/jira/browse/FALCON-389
Project: Falcon
Issue Type: Improvement
Affects Versions: 0.4
Reporter: Arpit Gupta
Noticed this on hadoop-2 with oozie 4.x that when you run an hcat replication
job where source and destination cluster's are different all jobs are submitted
to oozie on the destination cluster. Then oozie runs an table export job that
it submits to RM on cluster 1.
Now if the oozie server on the target cluster is not running with all hadoop
configs it will not know all the appropriate hadoop configs and yarn job will
fail. We saw jobs fail with errors like
org.apache.hadoop.security.token.SecretManager$InvalidToken: Password not found
for ApplicationAttempt appattempt_1395965672651_0010_000002
on unsecure cluster as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
