Database Reference
In-Depth Information
echo 1 > /data/zookeeper/myid
When all this is done, the ZooKeeper daemon can be started with using
the
zkServer.sh
script, found in ZooKeeper's
bin
subdirectory. The
zkServer.sh
script is set up like an
init.d
script and provides the usual
stop, start, and restart commands. It also has a start-foreground option that
is useful for development. This has the daemon log to the foreground rather
than a log file:
$ bin/zkServer.sh start-foreground
JMX enabled by default
Using config: /Users/bellis/Projects/zookeeper-3.4.5/
bin/../conf/zoo.cfg
[myid:] - INFO [main:QuorumPeerConfig@101] - Reading
configuration
from: /Users/bellis/Projects/zookeeper-3.4.5/bin/../
conf/zoo.cfg
[myid:] - INFO [main:DatadirCleanupManager@78] -
autopurge.snapRetainCount
[myid:] - INFO [main:DatadirCleanupManager@79] -
set to 0
[myid:] - INFO [main:DatadirCleanupManager@101] -
Purge task is not
autopurge.purgeInterval scheduled.
[myid:] - WARN [main:QuorumPeerMain@113] - Either no
config or no
quorum defined in config, running in standalone mode
[myid:] - INFO [main:QuorumPeerConfig@101] - Reading
configuration
from: /Users/bellis/Projects/zookeeper-3.4.5/bin/../
conf/zoo.cfg
[myid:] - INFO [main:ZooKeeperServerMain@95] -
Starting server
[myid:] - INFO [main:Environment@100] - Server
environment:zookeeper.version=3.4.5-1392090,
built on 09/30/2012 17:52 GMT
[myid:] - INFO [main:Environment@100] - Server
environment:host.name=byrons-air
[myid:] - INFO [main:Environment@100] - Server
