a, create missing path).
> >> > This initialization phase should only be executed once. In the current
> >> > singa architecture, there is no master node,
> >> > hence we need an external tool to do the job before launching singa.
> (We
> >> > are
current
>> > singa architecture, there is no master node,
>> > hence we need an external tool to do the job before launching singa. (We
>> > are planning to implement it next.)
>> >
>> > For your request of writing "hostfile" into zookeeper, it could
the current
> > singa architecture, there is no master node,
> > hence we need an external tool to do the job before launching singa. (We
> > are planning to implement it next.)
> >
> > For your request of writing "hostfile" into zookeeper, it could also be
>
or your request of writing "hostfile" into zookeeper, it could also be
> done by the same tool.
> Could you write your code as a new file /support/main.cc which we can later
> extend to be the tool.
>
> For the zookeeper API, it is included in the ZKClusterRT class in
> /uti
zookeeper, it could also be
done by the same tool.
Could you write your code as a new file /support/main.cc which we can later
extend to be the tool.
For the zookeeper API, it is included in the ZKClusterRT class in
/utils/cluster_rt.h.
I will make the create_zk_node a public function for you t
Hi guys,
Currently the standalone version (I followed the Quickstart guide) would
start Zookeeper service every time I ran "singa-run.sh".
I assume that on the distributed version, the ZK service will be started
only once by a master node, and the rest of the cluster will know the ZK
master addr
