[
https://issues.apache.org/jira/browse/SINGA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696397#comment-14696397
]
ASF subversion and git services commented on SINGA-56:
------------------------------------------------------
Commit 539fcee567cf597d8dae5e9c41a1b3b682db791f in incubator-singa's branch
refs/heads/master from wang sheng
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=539fcee ]
SINGA-56 No automatic launching of zookeeper service
disabled launching zk service in singa-run.sh
users need to explicitly start zookeeper
if use zk in /thirdparty, /bin/zk-service can be used to start/stop it
functionality of scripts are minor changed:
- singa-cleanup.sh now will not stop zookeeper
- singa-stop.sh now only remove /singa/app path in zk,
so it will not reset future job id to start from 0
> No automatic launching of zookeeper service
> -------------------------------------------
>
> Key: SINGA-56
> URL: https://issues.apache.org/jira/browse/SINGA-56
> Project: Singa
> Issue Type: Task
> Reporter: Sheng Wang
>
> Currently, when running a singa job, we will automatically start zookeeper
> service if it is not on. This convenience users to run their jobs.
> However, we found that, with incorrect configurations, this might launch
> unused zk services when users not intend to do so.
> We decide to let user explicitly start their zk service, so it is much easy
> to manage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
