falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1165) Falcon restart failed, if defined service in cluster entity is unreachable
Date Thu, 07 May 2015 09:30:00 GMT

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

Pallavi Rao commented on FALCON-1165:
-------------------------------------

[~peeyushb] clarified over skype that the intent is to bring up Falcon server even if some
of the interfaces of a cluster are down (quite likely temporarily or for maintenance). Don't
intend to distinguish between local Hadoop cluster or remote. It was just a use case he quoted.

That sounds fair enough. Currently too, we bring up Falcon even when Oozie is down. As long
as we log during startup that Falcon was unable to communicate with some of the services,
it is fine.

> Falcon restart failed, if defined service in cluster entity is unreachable
> --------------------------------------------------------------------------
>
>                 Key: FALCON-1165
>                 URL: https://issues.apache.org/jira/browse/FALCON-1165
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>            Reporter: Peeyush Bishnoi
>            Assignee: Peeyush Bishnoi
>             Fix For: 0.7
>
>         Attachments: FALCON-1165.patch
>
>
> Falcon fail to restart, if any service in the cluster entity is not reachable or down.
> For example, if there are clusters X, Y, Z. In cluster X, submit cluster entities which
points to services of cluster Y & Z. Execute some replication jobs from cluster X to Y
and even to cluster Z as well. If after certain duration, cluster Z HDFS service is down due
to maintenance activity and at the same time we require to restart Falcon service on cluster
X due to some reason, then Falcon will fail to restart on cluster X. 
> This issue has been reported internally at Hortonworks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message