falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-437) Feed Replication workflows are failing
Date Sat, 10 May 2014 22:04:04 GMT

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

Venkatesh Seetharam commented on FALCON-437:
--------------------------------------------

I think I know the issue and is indeed a regression caused by FALCON-390. Will have a fix
soon. Need this for 0.5 branch as well. The sharelibs are copied into the parent folder but
the workflow is in a subfolder with target cluster name.

> Feed Replication workflows are failing
> --------------------------------------
>
>                 Key: FALCON-437
>                 URL: https://issues.apache.org/jira/browse/FALCON-437
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.5, 0.6
>            Reporter: Satish Mittal
>            Priority: Blocker
>             Fix For: 0.5
>
>         Attachments: FALCON-437.patch
>
>
> With latest trunk, feed replication workflows are failing with ClassNotFoundException
for falcon lib classes (LateDataHandler and FalconPostProcessing).
> Noticed that in mapred.job.classpath.files conf property of replication jobs, none of
falcon workflow lib jars are getting added. Hence the exception.
> Also noticed that when feed is scheduled, the lib folder is not getting created on HDFS
at default appPath location. 
> e.g. when replication appPath is:
> {noformat}
> ${nameNode}/projects/falcon/hcolo2/staging/falcon/workflows/feed/hcat-in-repl3/1399545050032/REPLICATION/hcat-cluster1
> {noformat}
> the lib folder is getting created at:
> {noformat}
> /projects/falcon/hcolo2/staging/falcon/workflows/feed/hcat-in-repl3/1399545050032/REPLICATION
> {noformat}
> It looks to be a regression due to FALCON-390.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message