mt-libcouchbase 1.4.0

data/ext/libcouchbase/doc/DoxygenLayout.xml

@@ -0,0 +1,109 @@
+<doxygenlayout version="1.0">
+  <!-- Navigation index tabs for HTML output -->
+  <navindex>
+    <tab type="mainpage" visible="yes" title=""/>
+    <tab type="modules" visible="yes" title="" intro=""/>
+    <tab type="namespaces" visible="yes" title="">
+      <tab type="namespacelist" visible="yes" title="" intro=""/>
+      <tab type="namespacemembers" visible="yes" title="" intro=""/>
+    </tab>
+    <tab type="classes" visible="no" title="">
+      <tab type="classlist" visible="no" title="" intro=""/>
+      <tab type="classindex" visible="no" title=""/>
+      <tab type="hierarchy" visible="yes" title="" intro=""/>
+      <tab type="classmembers" visible="no" title="" intro=""/>
+    </tab>
+    <tab type="globals" visible="yes" title="" intro=""/>
+    <tab type="files" visible="yes" title="">
+      <tab type="filelist" visible="yes" title="" intro=""/>
+    </tab>
+    <tab type="examples" visible="yes" title="" intro="Here is a list of examples. Find more at https://github.com/couchbaselabs/devguide-examples/tree/master/c"/>
+    <tab type="pages" visible="yes" title="" intro=""/>
+  </navindex>
+
+  <!-- Layout definition for a file page -->
+  <file>
+    <briefdescription visible="yes"/>
+    <includes visible="$SHOW_INCLUDE_FILES"/>
+    <includegraph visible="$INCLUDE_GRAPH"/>
+    <includedbygraph visible="$INCLUDED_BY_GRAPH"/>
+    <sourcelink visible="yes"/>
+    <memberdecl>
+      <classes visible="yes" title=""/>
+      <namespaces visible="yes" title=""/>
+      <defines title=""/>
+      <typedefs title=""/>
+      <enums title=""/>
+      <functions title=""/>
+      <variables title=""/>
+      <membergroups visible="yes"/>
+    </memberdecl>
+    <detaileddescription title=""/>
+    <memberdef>
+      <inlineclasses title=""/>
+      <defines title=""/>
+      <typedefs title=""/>
+      <enums title=""/>
+      <functions title=""/>
+      <variables title=""/>
+    </memberdef>
+    <authorsection/>
+  </file>
+
+  <!-- Layout definition for a group page -->
+  <group>
+    <detaileddescription title=""/>
+    <briefdescription visible="no"/>
+    <groupgraph visible="$GROUP_GRAPHS"/>
+    <memberdecl>
+      <nestedgroups visible="yes" title=""/>
+      <dirs visible="no" title=""/>
+      <files visible="yes" title=""/>
+      <namespaces visible="no" title=""/>
+      <functions title="" visible="no"/>
+      <classes visible="no" title=""/>
+      <defines title="" visible="no"/>
+      <typedefs title="" visible="no"/>
+      <enums title="" visible="no"/>
+      <enumvalues title="" visible="no"/>
+      <variables title=""/>
+      <signals title=""/>
+      <publicslots title=""/>
+      <protectedslots title=""/>
+      <privateslots title=""/>
+      <events title=""/>
+      <properties title=""/>
+      <friends title=""/>
+      <membergroups visible="yes"/>
+    </memberdecl>
+    <memberdef>
+      <pagedocs/>
+      <functions title=""/>
+      <inlineclasses title=""/>
+      <defines title=""/>
+      <typedefs title=""/>
+      <enums title=""/>
+      <enumvalues title=""/>
+      <variables title=""/>
+      <signals title=""/>
+      <publicslots title=""/>
+      <protectedslots title=""/>
+      <privateslots title=""/>
+      <events title=""/>
+      <properties title=""/>
+      <friends title=""/>
+    </memberdef>
+    <authorsection visible="yes"/>
+  </group>
+
+  <!-- Layout definition for a directory page -->
+  <directory>
+    <briefdescription visible="yes"/>
+    <directorygraph visible="yes"/>
+    <memberdecl>
+      <dirs visible="yes"/>
+      <files visible="yes"/>
+    </memberdecl>
+    <detaileddescription title=""/>
+  </directory>
+</doxygenlayout>

data/ext/libcouchbase/doc/Makefile

@@ -0,0 +1,44 @@
+SRCROOT=$(shell pwd)
+VERSINFO=$(shell $(SRCROOT)/packaging/parse-git-describe.pl --tar)
+ifneq ($(strip $(VERSINFO)),)
+  VERLINE=PROJECT_NUMBER=$(VERSINFO)
+endif
+
+DOXYGEN?=doxygen
+DOXYFILE=doc/Doxyfile
+OUTDIR_PUB = doc/public
+OUTDIR_PRIV = doc/internal
+INTERNAL_SRC = \
+			   src/rdb \
+			   src/bootstrap.h \
+			   src/lcbio \
+			   src/netbuf \
+			   src/mc \
+			   src/retryq.h \
+			   src/bucketconfig/clconfig.h \
+			   src/mcserver \
+			   src/list.h \
+			   src/sllist.h \
+			   src/sllist-inl.h \
+			   src/hostlist.h \
+			   include/memcached/protocol_binary.h
+
+all: public internal
+public:
+	(cat $(DOXYFILE);\
+		echo $(VERLINE);\
+		echo OUTPUT_DIRECTORY=$(OUTDIR_PUB)) | $(DOXYGEN) -
+	cp doc/style.css $(OUTDIR_PUB)/html/style.css
+
+
+
+internal:
+	(cat $(DOXYFILE);\
+		echo $(VERLINE); \
+		echo OUTPUT_DIRECTORY=$(OUTDIR_PRIV); \
+		echo INTERNAL_DOCS=yes; \
+		echo INPUT += $(INTERNAL_SRC);) | $(DOXYGEN) -
+	cp doc/style.css $(OUTDIR_PRIV)/html/style.css
+
+clean:
+	rm -r -f $(OUTDIR_PRIV)/html $(OUTDIR_PUB)/html

data/ext/libcouchbase/doc/apiattr.h

@@ -0,0 +1,117 @@
+/* -*- Mode: C; tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*- */
+/*
+ *     Copyright 2010-2017 Couchbase, Inc.
+ *
+ *   Licensed under the Apache License, Version 2.0 (the "License");
+ *   you may not use this file except in compliance with the License.
+ *   You may obtain a copy of the License at
+ *
+ *       http://www.apache.org/licenses/LICENSE-2.0
+ *
+ *   Unless required by applicable law or agreed to in writing, software
+ *   distributed under the License is distributed on an "AS IS" BASIS,
+ *   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ *   See the License for the specific language governing permissions and
+ *   limitations under the License.
+ */
+
+/**
+ * @page lcb_attributes Interface Attributes
+ *
+ * Libcouchbase tries to follow the _release early, release often_
+ * philosophy. As part of that we want people to be able to try out new
+ * interfaces before we "stick" to them. Unfortunately this means that we
+ * discover that we need to change them in incompatible ways.
+ *
+ * To aid developers to make reasonable decisions on how likely we are to
+ * change these interfaces all functions in libcouchbase have an
+ * associated Interface Stability tag. If you find undocumented structs,
+ * functions or files you should *not* use them. They may be changed in
+ * incompatible ways without any notice. Unless explicitly noted the
+ * interface stability applies to both source code and binaries.
+ *
+ * This is a standard definition across all official Couchbase Server SDKs.
+ * @see https://developer.couchbase.com/documentation/server/current/sdk/c/compatibility-versions-features.html
+ *
+ * The following classifications exist:
+ *
+ * ### Committed
+ *
+ * A committed interface is the highest grade of stability, and is the
+ * preferred attribute level for consumers of the library. Couchbase
+ * tries at best effort to preseve committed interfaces between major
+ * versions of libcouchbase, and changes to committed interfaces within a
+ * major version is highly exceptional. Such exceptions may include
+ * situations where the interface may lead to data corruption, security
+ * holes etc.
+ *
+ * _This is the default interface level for an API, unless the API is specifically
+ * marked otherwise._
+ *
+ * ### Uncommitted
+ *
+ * No commitment is made about the interface (in binary or source
+ * form). It may be changed in incompatible ways and dropped from one
+ * release to another. The difference between an uncommitted interface
+ * and a volatile interface is its maturity and likelyhood of being
+ * changed. Uncommitted interfaces may mature into committed interfaces.
+ *
+ * ### Volatile
+ *
+ * Volatile interfaces can change at any time and for any reason.
+ *
+ * Interfaces may be volatile for reasons including:
+ *
+ * * Interface depends on specific implementation detail within the library
+ *   which may change in the future.
+ *
+ * * Interface depends on specific implementation detail within the server
+ *   which may change in the future.
+ *
+ * * Interface has been introduced as part of a trial phase for the specific
+ *   feature.
+ *
+ * ### Deprecated
+ *
+ * The interface is subject to be removed from future versions of
+ * libcouchbase. Interfaces may be deprecated for a variety of reasons, such
+ * as specific bugs found within the API itself, or a more uniform and/or
+ * direct method of achieving the same goal.
+ *
+ * ### Internal
+ *
+ * Internal interfaces are used internally in libcouchbase and should not
+ * be used elsewhere. Doing so may cause libcouchbase to misbehave.
+ *
+ * Unless otherwise noted, any API not found in the <include/libcouchbase>
+ * directory is considered to be internal.
+ *
+ * Some earlier versions of libcouchbase may have listed APIs as private,
+ * when the intended term in the taxonomy is internal.
+ *
+ * The listing of interfaces may be found here:
+ *
+ * * @subpage lcb_apiattr_committed
+ * * @subpage lcb_apiattr_uncommitted
+ * * @subpage lcb_apiattr_volatile
+ * * @subpage deprecated
+ * * @subpage lcb_apiattr_internal
+ **/
+
+/**
+ * @page lcb_apiattr_committed Committed Interfaces
+ * @see @ref lcb_attributes
+ *
+ * @page lcb_apiattr_uncommitted Uncomitted Interfaces
+ * @see @ref lcb_attributes
+ *
+ * @page lcb_apiattr_volatile Volatile Interfaces
+ * @see @ref lcb_attributes
+ *
+ * @page deprecated Deprecated Interfaces
+ * @see @ref lcb_attributes
+
+ * @page lcb_apiattr_internal Internal Interfaces
+ * @see @ref lcb_attributes
+ *
+ */

data/ext/libcouchbase/doc/cbc-n1qlback.markdown

@@ -0,0 +1,88 @@
+# cbc-n1qlback(1) - Stress Test for Couchbase Query (N1QL)
+
+## SYNOPSIS
+
+`cbc-n1qlback` -f QUERYFILE [_OPTIONS_]
+
+## DESCRIPTION
+
+`cbc-n1qlback` creates a specified number of threads each executing a set
+of user defined queries.
+
+`cbc-n1qlback` requires that it be passed the path to a file containing
+the queries to execute; one per line. The query should be in the format of
+the actual HTTP POST body (in JSON format) to be sent to the server.
+For simple queries, only the `statement` field needs to be set:
+
+    {"statement":"SELECT country FROM `travel-sample`"}
+    {"statement":"SELECT country, COUNT(country) FROM `travel-sample` GROUP BY country"}
+
+
+For more complex queries (for example, placeholders, custom options), you may
+refer to the N1QL REST API reference.
+
+`n1qlback` requires that any resources (data items, indexes) are already
+defined.
+
+## OPTIONS
+
+The following options control workload generation:
+
+* `-f` `--queryfile`=_PATH_:
+  Path to a file containing the query bodies to execute in JSON format, one
+  query per line. See above for the format.
+
+* `-t`, `--num-threads`=_NTHREADS_:
+  Set the number of threads (and thus the number of client instances) to run
+  concurrently. Each thread is assigned its own client object.
+
+
+The following options control how `cbc-n1qlback` connects to the cluster
+
+@@common-options.markdown@@
+
+* `-e`, `--error-log`=_PATH_:
+  Path to a file, where the command will write failed queries along with error details.
+  Use this option to figure out why `ERRORS` metric is not zero.
+
+
+<a name="additional-options"></a>
+## ADDITIONAL OPTIONS
+
+The following options may be included in the connection string (via the `-U`
+option) as URI-style query params (e.g.
+`couchbase://host/bucket?option1=value1&option2=value2`) or as individual
+key=value pairs passed to the `-D` switch (e.g. `-Doption1=value1
+-Doption2=value`). The `-D` will internally build the connection string,
+and is provided as a convenience for options to be easily passed on the
+command-line
+
+@@common-additional-options.markdown@@
+
+## EXAMPLES
+
+The following will create a file with 3 queries and 5 threads alternating
+between them. It also creates indexes on the `travel-sample` bucket
+
+    cbc n1ql -U couchbase://192.168.72.101/a_bucket 'CREATE INDEX ix_name ON `travel-sample`(name)'
+    cbc n1ql -U couchbase://192.168.72.101/a_bucket 'CREATE INDEX ix_country ON `travel-sample`(country)'
+
+    cat queries.txt <<EOF
+    {"statement":"SELECT country FROM `travel-sample` WHERE `travel-sample`.country = \"United States\""}
+    {"statement":"SELECT name FROM `travel-sample` LIMIT 10"}
+    {"statement":"SELECT country, COUNT(country) FROM `travel-sample` GROUP BY country"}
+    EOF
+
+    cbc-n1qlback -U couchbase://192.168.72.101/a_bucket -t 5 -f queries.txt
+
+## BUGS
+
+This command's options are subject to change.
+
+## SEE ALSO
+
+cbc(1), cbc-pillowfight(1), cbcrc(4)
+
+## HISTORY
+
+The `cbc-n1qlback` tool was first introduced in libcouchbase 2.4.10

data/ext/libcouchbase/doc/cbc-pillowfight.markdown

@@ -0,0 +1,296 @@
+# cbc-pillowfight(1) - Stress Test for Couchbase Client and Cluster
+
+## SYNOPSIS
+
+`cbc-pillowfight` [_OPTIONS_]
+
+## DESCRIPTION
+
+`cbc-pillowfight` creates a specified number of threads each looping and
+performing get and set operations within the cluster.
+
+The stress test operates in the following order
+
+1. It will pre-load the items in the cluster (set by the `--num-items` option)
+
+2. Once the items are all loaded into the cluster, it will access all the items
+(within the `--num-items`) specification, using a combination of storage and
+retrieval operations (the proportion of retrieval and storage operations are
+controlled via the `--set-pct` option).
+
+3. Operations are scheduled in _batches_. The batches represent a single pipeline
+(or network buffer) which is filled with a certain amount of operations (see the
+`--batch-size` option). These batch sizes are then sent over to the cluster and
+the requests are serviced by it.
+
+
+### Tuning
+
+Getting the right benchmark numbers highly depends on the type of environment
+the client is being run in. The following provides some information about
+specific settings which may make `pillowfight` generate more operations.
+
+* Increasing the batch size will typically speed up operations, but increasing
+  the batch size too much will actually slow it down. Additionally, very high
+  batch sizes will cause high memory usage.
+
+* Adding additional threads will create additional client objects and connections,
+  potentially increasing performance. Adding too many threads will cause local
+  and network resource congestion.
+
+* Decreasing the item sizes (the `--min-size` and `--max-size` options) will
+  always yield higher performance in terms of operationd-per-second.
+
+* Limiting the working set (i.e. `--num-items`) will decrease the working set
+  within the cluster, thereby increasing the chance that a given item will be
+  inside the server's CPU cache (which is extremely fast), rather than in main
+  memory (slower), or disk (much slower)
+
+The benchmark tool sets up SIGQUIT (CTRL-/) handler and dumps useful diagnostics
+and metrics to STDERR on this signal.
+
+## OPTIONS
+
+Options may be read either from the command line, or from a configuration file
+(see cbcrc(4)):
+
+The following options control workload generation:
+
+* `-B`, `--batch-size`=_BATCHSIZE_:
+  This controls how many commands are scheduled per cycles. To simulate one operation
+  at a time, set this value to 1.
+
+* `-I`, `--num-items`=_NUMITEMS_:
+  Set the _total_ number of items the workload will access within the cluster. This
+  will also determine the working set size at the server and may affect disk latencies
+  if set to a high number.
+
+* `-p`, `--key-prefix`=_PREFIX_:
+  Set the prefix to prepend to all keys in the cluster. Useful if you do not wish the items
+  to conflict with existing data.
+
+* `-t`, `--num-threads`=_NTHREADS_:
+  Set the number of threads (and thus the number of client instances) to run
+  concurrently. Each thread is assigned its own client object.
+
+* `-r`, `--set-pct`=_PERCENTAGE_:
+  The percentage of operations which should be mutations. A value of 100 means
+  only mutations while a value of 0 means only retrievals.
+
+* `-n`, `--no-population`:
+  By default `cbc-pillowfight` will load all the items (see `--num-items`) into
+  the cluster and then begin performing the normal workload. Specifying this
+  option bypasses this stage. Useful if the items have already been loaded in a
+  previous run.
+
+* `--populate-only`:
+  Stop after population. Useful to populate buckets with large amounts of data.
+
+* `-m`, `--min-size`=_MINSIZE_:
+* `-M`, `--max-size`=_MAXSIZE_:
+  Specify the minimum and maximum value sizes to be stored into the cluster.
+  This is typically a range, in which case each value generated will be between
+  `--min-size` and `--max-size` bytes.
+
+* `-E`, `--pause-at-end`:
+  When the workload completes, do not exit immediately, but wait for user input.
+  This is helpful for analyzing open socket connections and state.
+
+* `-c`, `--num-cycles`:
+  Specify the number of times the workload should cycle. During each cycle
+  an amount of `--batch-size` operations are executed. Setting this to `-1`
+  will cause the workload to run infinitely.
+
+* `--sequential`:
+  Specify that the access pattern should be done in a sequential manner. This
+  is useful for bulk-loading many documents in a single server.
+
+* `--start-at`:
+  This specifies the starting offset for the items. The items by default are
+  generated with the key prefix (`--key-prefix`) up to the number of items
+  (`--num-items`). The `--start-at` value will increase the lower limit of
+  the items. This is useful to resume a previously cancelled load operation.
+
+* `-T`, `--timings`:
+  Enabled timing recorded. Timing histogram will be dumped to STDERR on SIGQUIT
+  (CTRL-/). When specified second time, it will dump a histogram of command
+  timings and latencies to the screen every second.
+
+* `-e`, `--expiry`=_SECONDS_:
+  Set the expiration time on the document for _SECONDS_ when performing each
+  operation. Note that setting this too low may cause not-found errors to
+  appear on the screen.
+
+@@common-options.markdown@@
+
+* `p`, `--persist-to`=_NUMNODES_:
+  Wait until the item has been persisted to at least `NUMNODES` nodes' disk. If
+  `NUMNODES` is 1 then wait until only the master node has persisted the item for
+  this key. You may not specify a number greater than the number of nodes actually
+  in the cluster. `-1` is special value, which mean to use all available nodes.
+
+* `r` `--replicate-to`=_NREPLICAS_:
+  Wait until the item has been replicated to at least `NREPLICAS` replica nodes.
+  The bucket must be configured with at least one replica, and at least `NREPLICAS`
+  replica nodes must be online. `-1` is special value, which mean to use all
+  available replicas.
+
+* `--lock`=_TIME_:
+  This will retrieve and lock an item before update, making it inaccessible for
+  modification until the update completed, or `TIME` has passed.
+
+* `--json`:
+  Make `pillowfight` store document as JSON rather than binary. This will
+  allow the documents to nominally be analyzed by other Couchbase services
+  such as Query and MapReduce.
+
+  JSON documents are created by creating an empty JSON object (`{}`) and then
+  repeated populating it with `Field_%d` property names (where `%d` is `1` and
+  higher), and setting its value to a repeating asterisk `*` up to 16 times:
+
+        {
+            "Field_1": "****************",
+            "Field_2": "****************",
+            "Field_3": "****************",
+            "Field_4": "****************",
+            "Field_5": "********"
+        }
+
+  When using document size constraints, be aware that the minimum and maximum
+  sizes (`--min-size` and `--max-size`) are not strict limits, and that the
+  resultant sizes may be bigger or smaller by a few bytes in order to satisfy
+  the requirements of proper JSON syntax.
+
+* `--noop`:
+  Use couchbase NOOP operations when running the workload. This mode ignores
+  population, and all other document operations. Useful as the most lightweight
+  workload.
+
+* `--subdoc`:
+  Use couchbase sub-document operations when running the workload. In this
+  mode `pillowfight` will use Couchbase
+  [sub-document operations](http://blog.couchbase.com/2016/february/subdoc-explained)
+  to perform gets and sets of data. This option must be used with `--json`
+
+* `--pathcount`:
+  Specify the number of paths a single sub-document operation should contain.
+  By default, each subdoc operation operates on only a single path within the
+  document. You can specify multiple paths to atomically executed multiple
+  subdoc operations within a single command.
+
+  This option does not affect the `--batch-size` option as a subdoc command
+  is considered as a single command (with respect to batching) regardless of
+  how many operations it contains.
+
+<a name="additional-options"></a>
+## ADDITIONAL OPTIONS
+
+The following options may be included in the connection string (via the `-U`
+option) as URI-style query params (e.g.
+`couchbase://host/bucket?option1=value1&option2=value2`) or as individual
+key=value pairs passed to the `-D` switch (e.g. `-Doption1=value1
+-Doption2=value`). The `-D` will internally build the connection string,
+and is provided as a convenience for options to be easily passed on the
+command-line
+
+@@common-additional-options.markdown@@
+
+## EXAMPLES
+
+### CONNECTION EXAMPLES
+
+The following examples show how to connect `pillowfight` to different types
+of cluster configurations.
+
+Connect to a bucket (`a_bucket`) on a cluster on a remote host (for servers version 5.x+).
+It uses account 'myname' and asks password interactively:
+
+    cbc-pillowfight -U couchbase://192.168.33.101/a_bucket -u myname -P-
+
+Run against a password-less bucket (`a_bucket`) on a cluster on a remote host (for servers older than 5.x):
+
+    cbc-pillowfight -U couchbase://192.168.33.101/a_bucket
+
+Connect to an SSL cluster at `secure.net`. The certificate for the cluster is
+stored locally at `/home/couchbase/couchbase_cert.pem`:
+
+    cbc-pillowfight -U couchbases://secure.net/topsecret_bucket?certpath=/home/couchbase/couchbase_cert.pem
+
+Connect to an SSL cluster at `secure.net`, ignoring certificate verification.
+This is insecure but handy for testing:
+
+    cbc-pillowfight -U couchbases://secure.net/topsecret_bucket?ssl=no_verify
+
+Connect to a password protected bucket (`protected`) on a remote host (for servers older than 5.x):
+
+    cbc-pillowfight -U couchbase://remote.host.net/protected -P -
+    Bucket password:
+    ...
+
+Connect to a password protected bucket (for servers older than 5.x), specifying the password on the
+command line (INSECURE, but useful for testing dummy environments)
+
+    cbc-pillowfight -U couchbase://remote.host.net/protected -P t0ps3cr3t
+
+Connect to a bucket running on a cluster with a custom REST API port
+
+    cbc-pillowfight -U http://localhost:9000/default
+
+Connec to bucket running on a cluster with a custom memcached port
+
+    cbc-pillowfight -U couchbase://localhost:12000/default
+
+Connect to a *memcached* (http://memcached.org)
+cluster using the binary protocol. A vanilla memcached cluster is not the same
+as a memcached bucket residing within a couchbase cluster (use the normal
+`couchbase://` scheme for that):
+
+    cbc-pillowfight -U memcached://host1,host2,host3,host4
+
+Connect to an SSL cluster at `secure.net`:
+
+    cbc-pillowfight -U couchbases://secure.net/topsecret_bucket
+
+
+Run against a bucket (`a_bucket`) on a cluster on a remote host:
+
+    cbc-pillowfight -U couchbase://192.168.33.101/a_bucket
+
+### BENCHMARK EXAMPLES
+
+The following examples show how to configure different types of workloads with
+pillowfight.
+
+Run with 20 threads/instances, each doing one operation at a time:
+
+    cbc-pillowfight -t 20 -B 1
+
+Run 100 iterations of 2MB item sizes, using a dataset of 50 items
+
+    cbc-pillowfight -M $(1024*1024) -m $(1024*1024) -c 100 -I 50
+
+Use JSON documents of 100k each
+
+    cbc-pillowfight --json -m 100000 -M 100000
+
+Stress-test sub-document mutations
+
+    cbc-pillowfight --json --subdoc --set-pct 100
+
+
+## TODO
+
+Rather than spawning threads for multiple instances, offer a way to have multiple
+instances function cooperatively inside an event loop.
+
+## BUGS
+
+This command's options are subject to change.
+
+## SEE ALSO
+
+cbc(1), cbcrc(4)
+
+## HISTORY
+
+The `cbc-pillowfight` tool was first introduced in libcouchbase 2.0.7