anchor.diff:  *Jepsen DB node* roles. The machine where the above mentioned maven command
   is run plays *Jepsen control node* role.
   
  +=== A reference script to build Kudu and run Jepsen tests
  +The following link:../../src/kudu/scripts/jepsen.sh[Bourne-again shell script]
  +can be used as a reference to build Kudu from source and run Jepsen tests.
  +
   === Troubleshooting
   When Jepsen's analysis doesn't find inconsistencies in the history of operations
   it outputs the following in the end of a test:
  
positive.code: 21:41:42 0 failures, 10 errors.
  ----
  To get more details, take a closer look at the output of `mvn clojure:run`
  or at particular `jepsen.log` files under
  $KUDU_HOME/java/kudu-jepsen/store/rw-register/<test_timestamp> directories.
  
  The latter class represents more serious issue: a manifestation of
  non-linearizable history of operations. This is reported as _failure_ in the
  
negative.code: To troubleshoot, first it's necessary to find where the failed test stores
  the results: it should be one of the timestamp-named sub-directories
  (e.g. `20170109T071938.000-0800`) under
  `$KUDU_HOME/java/kudu-jepsen/store/rw-register` in case of a linearizability
  failure in one of the `rw-register` test scenarios. One of the possible ways
  to find the directory:
  [listing]
  ----
  