xapian-replicate(1) [debian man page]

XAPIAN-REPLICATE(1)						   User Commands					       XAPIAN-REPLICATE(1)

NAME

       xapian-replicate - Replicate a database from a master server to a local copy

SYNOPSIS

       xapian-replicate [OPTIONS] DATABASE

DESCRIPTION

       xapian-replicate - Replicate a database from a master server to a local copy

OPTIONS

       -h, --host=HOST
	      host to connect to (required)

       -p, --port=PORT
	      port to connect to (required)

       -m, --master=DB
	      replicate database DB from the master (default: DATABASE)

       -i, --interval=N
	      wait N seconds between each connection to the master (default: 60)

       -r, --reader-time=N wait N seconds to allow readers time to close before
	      applying repeated changesets (default: 30)

       -o, --one-shot
	      replicate only once and then exit

       -v, --verbose
	      be more verbose

       --help display this help and exit

       --version
	      output version information and exit

xapian-core 1.2.12						     June 2012						       XAPIAN-REPLICATE(1)

KUMO-SERVER(1)						      General Commands Manual						    KUMO-SERVER(1)

NAME

       kumo-server - kumofs server daemon

SYNOPSIS

       kumo-server -m <addr[:port=19700]> -p <addr[:port19700]> -l <addr[:port=19800]> -s <path.tch>

DESCRIPTION

       kumo-server  stores  actual  data.  You	can add kumo-servers after buiding the cluster.  You can get live status of the kumo-manager using
       kumostat and kumotop command.

OPTIONS

       -l <addr[:port=19800]> --listen
	      listen address

       -L <port=19900> --stream-listen
	      listen port for replacing stream

       -f <dir=/tmp> --offer-tmp
	      path to temporary directory for replacing

       -s <path.tch> --store
	      path to database

       -m <addr[:port=19700]> --manager1
	      address of manager 1

       -p <addr[:port=19700]> --manager2
	      address of manager 2

       -S <number=20> --replicate-set-retry
	      replicate set retry limit

       -D <number=20> --replicate-delete-retry
	      replicate delete retry limit

       -gN <seconds=60> --garbage-min-time
	      minimum time to maintenance deleted key

       -gX <seconds=3600> --garbage-max-time
	      maximum time to maintenance deleted key

       -gS <kilobytes=2048> --garbage-mem-limit
	      maximum memory usage to memory deleted key

       -k <number=2> --keepalive-interval
	      keepalive interval in seconds

       -Ys <number=1> --connect-timeout
	      connect timeout time in seconds

       -Yn <number=4> --connect-retry-limit
	      connect retry limit

       -Ci <number=8> --clock-interval
	      clock interval in seconds

       -TW <number=2> --write-threads
	      number of threads for asynchronous writing

       -TR <number=4> --read-threads
	      number of threads for asynchronous reading

       -o <path.log> --log
	      output logs to the file

       -g <path.mpac> --binary-log
	      enable binary log

       -v --verbose

       -d <path.pid> --daemon

EXAMPLE

       [on svr1  ]$ kumo-server -v -l svr1 -m mgr1 -p mgr2 -s /var/kumodb.tch -gN 5 -gS 20480

       [on svr2  ]$ kumo-server -v -l svr2 -m mgr1 -p mgr2 -s /var/kumodb.tch -TR 6 -TW 4

       [on svr3  ]$ kumo-server -v -l svr3 -m mgr1 -p mgr2 -s /var/kumodb.tch -Ci 16

       [localhost]$ kumo-server  -v -m localhost -l localhost:19801 -L 19901 -s ./database1.tch

       [localhost]$ kumo-server  -v -m localhost -l localhost:19802 -L 19902 -s ./database2.tch

       [localhost]$ kumo-server  -v -m localhost -l localhost:19803 -L 19902 -s ./database3.tch

SEE ALSO

       kumostat(1), kumotop(1), kumolog(1), kumomergedb(1), kumohash(1).

kumo-server							     July 2009							    KUMO-SERVER(1)