You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@singa.apache.org by "Sheng Wang (JIRA)" <ji...@apache.org> on 2015/05/28 10:56:17 UTC

[jira] [Commented] (SINGA-5) Server early terminate when zookeeper singa folder is not initially empty

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

Sheng Wang commented on SINGA-5:
--------------------------------

bug fixed in commit: http://git-wip-us.apache.org/repos/asf/incubator-singa/commit/6bcaaaa4

> Server early terminate when zookeeper singa folder is not initially empty
> -------------------------------------------------------------------------
>
>                 Key: SINGA-5
>                 URL: https://issues.apache.org/jira/browse/SINGA-5
>             Project: Singa
>          Issue Type: Bug
>            Reporter: Sheng Wang
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Ideally, when a singa process crashes, its registered (ephemeral) file in zookeeper will be automatically deleted.
> However, this deletion will be executed after a TIME_OUT time. Hence, if we rerun singa immediately, the server will get a phantom worker. If this is the only registered worker when the file is finally deleted, the server will think all workers have been left. It may terminate its service, before worker starts to execute.



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