falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-2280) Unable to create mirror on WASB target due to "Cluster entity not found"
Date Fri, 10 Feb 2017 04:57:41 GMT

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

ASF GitHub Bot commented on FALCON-2280:
----------------------------------------

GitHub user sowmyaramesh opened a pull request:

    https://github.com/apache/falcon/pull/365

    FALCON-2280 Unable to create mirror on WASB target using extensions

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sowmyaramesh/falcon FALCON-2280

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/365.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #365
    
----
commit 96fd8400dffa55c1991fe98af54bb0092f04c679
Author: Sowmya Ramesh <sramesh@hortonworks.com>
Date:   2017-02-10T04:55:27Z

    FALCON-2280 Unable to create mirror on WASB target using extensions

----


> Unable to create mirror on WASB target due to "Cluster entity not found"
> ------------------------------------------------------------------------
>
>                 Key: FALCON-2280
>                 URL: https://issues.apache.org/jira/browse/FALCON-2280
>             Project: Falcon
>          Issue Type: Bug
>          Components: extensions
>            Reporter: Sowmya Ramesh
>            Assignee: Sowmya Ramesh
>             Fix For: trunk
>
>
> 1. Create a mirror which source cluster is the one created , and dummy target cluster

> 2. Save
> Submitting the mirror from CLI (see log below):
> 1) with WASB url on "targetCluster", it complained that the WASB was invalid 
> or 
> 2) with nothing on "targetCluster", it complained that "Cluster entity not found" 
> # cat /tmp/hdfsMirroring.props
> jobName=testjob 
> jobClusterName=primaryCluster 
> jobValidityStart=2017-01-13T00:00Z 
> jobValidityEnd=2017-12-30T00:00Z 
> jobFrequency=minutes(5) 
> sourceDir=/data/testdir 
> sourceCluster=primaryCluster
> targetDir=/data/testdir 
> targetCluster= 
>  # su - falcon 
> # /usr/hdp/current/falcon-server/bin/falcon extension -submit -extensionName hdfs-mirroring
-file /tmp/hdfsMirroring.props
> ERROR: Internal Server Error;Cluster entity not found 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message