falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-389) Submit Hcat export workflow to oozie on source cluster rather than to oozie on destination cluster
Date Fri, 11 Apr 2014 18:24:21 GMT

    [ https://issues.apache.org/jira/browse/FALCON-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966924#comment-13966924
] 

Arpit Gupta commented on FALCON-389:
------------------------------------

Another issue which is related is FALCON-401. If we could run the export job through the source
oozie then you would not need to run the same export job twice if you have multiple targets.

> 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)

Mime
View raw message