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-109) submission of clusters for non registered colos
Date Wed, 30 Apr 2014 00:14:14 GMT

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

Venkatesh Seetharam commented on FALCON-109:

What should the expected behavior be for stand alone mode? Enforce colo to be local or default?

> submission of clusters for non registered colos 
> ------------------------------------------------
>                 Key: FALCON-109
>                 URL: https://issues.apache.org/jira/browse/FALCON-109
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.3
>         Environment: QA
>            Reporter: Samarth Gupta
> in the cluster definition we have a tag "colo" . If the value provided for this tag is
not one of the colos mentioned in prism runtime properties, submission of cluster is successful.
But any subsequent submission on feed / process for that cluster fails as its endpoints does
not exists. 
> Also user is not able to delete the cluster since falcon tries to delete it from a non
existent colo. In addition to this if user tried to submit a feed and whose submission failed,
it also can not be deleted. 
> Below is the message 
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><status>FAILED</status><message>gs/org.apache.falcon.FalconException::com.sun.jersey.api.client.ClientHandlerException:
java.lang.IllegalArgumentException: URI is not absolute
> </message><requestId>gs/de363c3b-3bba-45ac-b47c-05c2d3c44409
> </requestId></result>
> now cluster can not be deleted since a feed depends on it. 
> and feed can not be deleted since cluster does not exists 

This message was sent by Atlassian JIRA

View raw message