"Fossies" - the Fresh Open Source Software Archive

Member "apache-zookeeper-3.8.1/zookeeper-it/README.txt" (25 Jan 2023, 2710 Bytes) of package /linux/misc/apache-zookeeper-3.8.1.tar.gz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the last Fossies "Diffs" side-by-side code changes report for "README.txt": 3.6.0_vs_3.6.1.

    1 To run the system test we need to create processing containers that we can
    2 spawn tasks, called Instances, in. (how is that for a dangling preposition!?!)
    3 Start up InstanceContainers first. Then run the system test. The system test
    4 finds the InstanceContainers and directs them through ZooKeeper, so you are
    5 going to need an instance of ZooKeeper running that they can all access.
    6 The easiest way to do all of this is to use the zookeeper fat jar.
    7 
    8 Steps to run system test
    9 ------------------------
   10 1) build and transfer the fatjar from the `zookeeper-contrib/zookeeper-contrib-fatjar/target`
   11    directory to all systems participating in the test
   12 
   13    Command to build fatjar without executing the tests:
   14 
   15    `mvn clean install -P fatjar -DskipTests`
   16 
   17 2) run a zookeeper standalone instance (cluster is ok too)
   18 
   19 e.g. java -jar zookeeper-<version>-fatjar.jar server <zoo.cfg>
   20 
   21 Note: you must provide zoo.cfg, see sample in conf directory
   22 
   23 3) on each host start the system test container
   24 
   25 e.g. java -jar zookeeper-<version>-fatjar.jar ic <name> <zkHostPort> /sysTest
   26 
   27 name : name of the test container - must be unique 
   28   typically it's a good idea to name after the host to aid debugging
   29 
   30 zkHostPort : the host:port of the server from step 2)
   31 
   32 4) initiate the system test using the fatjar:
   33 
   34 java -jar build/contrib/fatjar/zookeeper-<version>-fatjar.jar systest org.apache.zookeeper.test.system.SimpleSysTest
   35 
   36 by default it will access the zk server started in 2) on localhost:2181 
   37 
   38 or you can specify a remote host:port using
   39   -DsysTest.zkHostPort=<host>:<port>,<host>:<port>,...
   40 
   41 java -DsysTest.zkHostPort=hostA:2181  -jar build/contrib/fatjar/zookeeper-<version>-fatjar.jar systest org.apache.zookeeper.test.system.SimpleSysTest
   42 
   43 where hostA is running the zk server started in step 2) above
   44 
   45 InstanceContainers can also be used to run a the saturation benchmark. The
   46 first two steps are the same as the system test. Step 3 is almost the same:
   47 
   48 3) start the InstanceContainer on each host:
   49 
   50 e.g. java -jar zookeeper-<version>-fatjar.jar ic <name> <zkHostPort> <prefix>
   51 
   52 note prefix can be /sysTest or any other path. If you do use /sysTest, make
   53 sure the system test isn't running when you run the benchmark.
   54 
   55 4) run GenerateLoad using the following
   56 
   57 java -jar build/contrib/fatjar/zookeeper-<version>-fatjar.jar generateLoad <zkHostPort> <prefix> #servers #clients
   58 
   59 Once GenerateLoad is started, it will read commands from stdin. Usually
   60 the only command you need to know is "percentage" which sets the percentage
   61 of writes to use in the requests. Once a percentage is set, the benchmark
   62 will start. "percentage 0" will cause only reads to be issued and
   63 "percentage 100" will cause only writes to be issued.