You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/11/14 13:03:33 UTC
[jira] [Commented] (FALCON-558) Cluster submission failure
[ https://issues.apache.org/jira/browse/FALCON-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212204#comment-14212204 ]
Venkatesh Seetharam commented on FALCON-558:
--------------------------------------------
[~pragya.mittal] do you still have issues submitting a cluster entity?
> Cluster submission failure
> --------------------------
>
> Key: FALCON-558
> URL: https://issues.apache.org/jira/browse/FALCON-558
> Project: Falcon
> Issue Type: Bug
> Components: general
> Reporter: Pragya Mittal
> Attachments: cluster.xml
>
>
> In the attached cluster definition, activemq port value is incorrect. So while submitting this cluster on distributed environment having 3 servers (say ua1,ua2,ua3) cluster gets submitted on ua2 and ua3 but throws error for ua1. Error is as follows :
> {code}
> dataqa@ip-192-168-138-34:~/rollUp$ falcon entity -type cluster -submit -file cluster.xml
> Error: Bad Request;ua1/Invalid Messaging server or port: tcp://localhost:61616?daemon=true for: org.apache.activemq.ActiveMQConnectionFactory
> Could not connect to broker URL: tcp://localhost:61616?daemon=true. Reason: java.net.ConnectException: Connection refused
> ua3/Submit successful (cluster) rollupCluster
> ua2/Submit successful (cluster) rollupCluster
> {code}
> On modifying cluster definition and resubmitting it,'Bad Request' error is thrown saying cluster is submitted on ua1. Below is the related response:
> {code}
> dataqa@ip-192-168-138-34:~/rollUp$ falcon entity -type cluster -submit -file cluster.xml
> Error: Bad Request;ua1/Submit successful (cluster) rollupCluster
> ua3/(cluster) rollupCluster already registered with configuration store. Can't be submitted again. Try removing before submitting.
> ua2/(cluster) rollupCluster already registered with configuration store. Can't be submitted again. Try removing before submitting.
> {code}
> Although on doing a cluster list, the cluster is not present leading to failure of feeds and process submission.
> {code}
> dataqa@ip-192-168-138-34:~/rollUp$ falcon entity -type feed -submit -file FETL-ImpressionRC.xml
> Error: Bad Request;rollupCluster (CLUSTER) not found
> {code}
> Below are the prism logs :
> {code}
> figuring client with /usr/lib/falcon/falconPrism/conf/prism.keystore (SecureHTTPChannel:56)
> 2014-07-30 07:06:00,572 ERROR - [1355316735@qtp-1333256886-218:dataqa:POST//entities/submit/cluster 8bf50501-7e22-451e-923d-bc9ac7612f7f] ~ Request failed: 400 (HTTPChannel:104)
> 2014-07-30 07:06:00,575 ERROR - [1355316735@qtp-1333256886-218:dataqa:POST//entities/submit/cluster 8bf50501-7e22-451e-923d-bc9ac7612f7f] ~ Action failed: Bad Request
> Error: ua1/Submit successful (cluster) rollupCluster
> ua3/(cluster) rollupCluster already registered with configuration store. Can't be submitted again. Try removing before submitting.
> ua2/(cluster) rollupCluster already registered with configuration store. Can't be submitted again. Try removing before submitting.
> (FalconWebException:60)
> 2014-07-30 07:06:00,575 INFO - [1355316735@qtp-1333256886-218:dataqa:POST//entities/submit/cluster 8bf50501-7e22-451e-923d-bc9ac7612f7f] ~ {Action:submit, Dimensions:{entityType=cluster, colo=NULL}, Status: FAILED, Time-taken:437717150 ns} (METRIC:33)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)