You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Bowen Zhang (JIRA)" <ji...@apache.org> on 2014/09/11 01:51:33 UTC
[jira] [Assigned] (OOZIE-1564) Metadata for dead Oozie servers
should remain in ZK
[ https://issues.apache.org/jira/browse/OOZIE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bowen Zhang reassigned OOZIE-1564:
----------------------------------
Assignee: Bowen Zhang (was: Robert Kanter)
> Metadata for dead Oozie servers should remain in ZK
> ---------------------------------------------------
>
> Key: OOZIE-1564
> URL: https://issues.apache.org/jira/browse/OOZIE-1564
> Project: Oozie
> Issue Type: Improvement
> Components: HA
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Bowen Zhang
>
> As per the discussion in OOZIE-1561, we should have two services in the service discovery on ZK:
> # Contains the metadata for any Oozie server that has ever connected, even ones that are currently dead
> #- This would be used by log streaming so that dead servers are always identified
> #- I think there is an easy way to do this with a setting in Curator, but I have to test it. If not, then we'll have to manually create/manage the ZNodes.
> # Contains the metadata for any Oozie server that is still alive (the current behavior)
> #- This would be used by the mod calculation so only alive servers are included
> Maintaining two lists will avoid the need to do any pinging or tricky heartbeating.
> We'd have to add a new admin command to cleanup the dead servers. It would look at which servers are not in the alive list and remove those.
> It would also be good to update the admin command that lists servers to specify which ones are alive and which are dead; and possibly have filtering (i.e. show only alive servers, show only dead servers, show all servers)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)