[
https://issues.apache.org/jira/browse/FALCON-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532036#comment-14532036
]
Pallavi Rao commented on FALCON-1165:
-------------------------------------
Help me understand. If cluster1 is on colo1 and cluster2 is on colo2, Falcon
server on colo1 won't even attempt to load cluster2 (coz., it is not
responsible for cluster2). Lets say, Falcon server on colo1 has clusters
cluster1 and cluster2. cluster1 talking to HDFS on the same colo and cluster2
talking to HDFS on a different colo (remote). During reload, both cluster1 and
cluster2 will be reloaded by the Falcon Server on colo1. How are we
distinguishing whether cluster1 or cluster2 is talking to local HDFS or remote
HDFS?
Is this what we are tying to solve?
> 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)
