svn commit: r1381891 - in /zookeeper/bookkeeper/branches/branch-4.1: CHANGES.txt doc/bookkeeperConfig.textile

[si...@apache.org]

Author: sijie
Date: Fri Sep  7 05:57:52 2012
New Revision: 1381891

URL: http://svn.apache.org/viewvc?rev=1381891&view=rev
Log:
BOOKKEEPER-354: [BOOKKEEPER-296] [Documentation] Modify the bookkeeper start script and document the bookkeeper stop command in bookkeeperConfig.xml (Kiran BC via sijie)

Modified:
    zookeeper/bookkeeper/branches/branch-4.1/CHANGES.txt
    zookeeper/bookkeeper/branches/branch-4.1/doc/bookkeeperConfig.textile

Modified: zookeeper/bookkeeper/branches/branch-4.1/CHANGES.txt
URL: http://svn.apache.org/viewvc/zookeeper/bookkeeper/branches/branch-4.1/CHANGES.txt?rev=1381891&r1=1381890&r2=1381891&view=diff
==============================================================================
--- zookeeper/bookkeeper/branches/branch-4.1/CHANGES.txt (original)
+++ zookeeper/bookkeeper/branches/branch-4.1/CHANGES.txt Fri Sep  7 05:57:52 2012
@@ -40,6 +40,8 @@ Release 4.1.1 - UNRELEASED
 
         BOOKKEEPER-372: Check service name in bookie start/stop script. (nijel via sjie)
 
+        BOOKKEEPER-354: [BOOKKEEPER-296] [Documentation] Modify the bookkeeper start script and document the bookkeeper stop command in bookkeeperConfig.xml (Kiran BC via sijie)
+
       hedwig-server:
 
         BOOKKEEPER-329: provide stop scripts for hub server (sijie)

Modified: zookeeper/bookkeeper/branches/branch-4.1/doc/bookkeeperConfig.textile
URL: http://svn.apache.org/viewvc/zookeeper/bookkeeper/branches/branch-4.1/doc/bookkeeperConfig.textile?rev=1381891&r1=1381890&r2=1381891&view=diff
==============================================================================
--- zookeeper/bookkeeper/branches/branch-4.1/doc/bookkeeperConfig.textile (original)
+++ zookeeper/bookkeeper/branches/branch-4.1/doc/bookkeeperConfig.textile Fri Sep  7 05:57:52 2012
@@ -26,12 +26,16 @@ For performance, we require each server 
 
 For ZooKeeper, there is no constraint with respect to the number of replicas. Having a single machine running ZooKeeper in standalone mode is sufficient for BookKeeper. For resilience purposes, it might be a good idea to run ZooKeeper in quorum mode with multiple servers. Please refer to the ZooKeeper documentation for detail on how to configure ZooKeeper with multiple replicas.
 
-h2. Running bookies
+h2. Starting and Stopping Bookies
 
-To run a bookie, we execute the following command:
+To *start* a bookie, execute the following command:
 
+* To run a bookie in the foreground:
 @bookkeeper-server/bin/bookkeeper bookie@
 
+* To run a bookie in the background:
+@bookkeeper-server/bin/bookkeeper-daemon.sh start bookie@
+
 The configuration parameters can be set in bookkeeper-server/conf/bk_server.conf.
 
 The important parameters are:
@@ -43,6 +47,11 @@ The important parameters are:
 
 Ideally, @journalDir@ and @ledgerDir@ are each in a different device. See "Bookie Configuration Parameters":./bookieConfigParams.html for a full list of configuration parameters.
 
+To *stop* a bookie running in the background, execute the following command:
+
+@bookkeeper-server/bin/bookkeeper-daemon.sh stop bookie [-force]@
+@-force@ is optional, which is used to stop the bookie forcefully, if the bookie server is not stopped gracefully within the _BOOKIE_STOP_TIMEOUT_ (environment variable), which is 30 seconds, by default.
+
 h3. Upgrading
 
 From time to time, we may make changes to the filesystem layout of the bookie, which are incompatible with previous versions of bookkeeper and require that directories used with previous versions are upgraded. If you upgrade your bookkeeper software, and an upgrade is required, then the bookie will fail to start and print an error such as: