[
https://issues.apache.org/jira/browse/FALCON-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088719#comment-15088719
]
Pallavi Rao edited comment on FALCON-1662 at 1/8/16 5:14 AM:
-------------------------------------------------------------
A state (scheduled, suspended) is associated with an entity, hence, we'll need
to use EntityID.
However, on second thoughts, state store might be fine just using EntityID as
long as we ensure we can have a single entity scheduled on multiple clusters on
single Falcon Server.
was (Author: pallavi.rao):
A state (scheduled, suspended) is associated with an entity, hence, we'll need
to use EntityID.
However, on second thoughts, state store might be fine just using EntityID as
long as we ensure we can a single entity can be scheduled on multiple clusters
on single Falcon Server.
> State Store should store EntityCluster ID rather than EntityID
> --------------------------------------------------------------
>
> Key: FALCON-1662
> URL: https://issues.apache.org/jira/browse/FALCON-1662
> Project: Falcon
> Issue Type: Sub-task
> Components: scheduler
> Reporter: Pallavi Rao
> Assignee: pavan kumar kolamuri
> Fix For: 0.9
>
>
> A single Falcon Server (colo) can have multiple clusters, hence, the cluster
> information should be part of the State store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
