[
https://issues.apache.org/jira/browse/OOZIE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844801#comment-13844801
]
Rohini Palaniswamy commented on OOZIE-1492:
-------------------------------------------
We don't have any cycles till mid Jan. The concern is they have in-memory data
structures. In case of HCat, there is a map that maintains the dependencies
that we are waiting on when the coord action is materialized. So we need to
ensure that the same hcat server that materialized the action runs input check
and launches job. In case of SLA, we have a map which is used to track SLA for
the jobs. We fall back to database to check if we did not get job status
events. So if job ran on another server, it will be inefficient as we will go
to database but alert will be sent out fine. But in case of restart, it loads
all pending jobs which have sla tracking from the table into memory. We will
have to split that between HA servers based on what jobs they will process.
> Make sure HA works with HCat and SLA notifications
> --------------------------------------------------
>
> Key: OOZIE-1492
> URL: https://issues.apache.org/jira/browse/OOZIE-1492
> Project: Oozie
> Issue Type: Improvement
> Components: HA
> Affects Versions: trunk
> Reporter: Robert Kanter
>
> We need to make sure HA works with HCat integration and SLA notifications.
> Both have in-memory datastructures and HA will impact them.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
