Shikhar Bhushan

RocksDB provides a [Comparator](https://github.com/facebook/rocksdb/wiki/Basic-Operations#comparators) API to customize key ordering. There is a note on [backwards compatibility](https://github.com/facebook/rocksdb/wiki/Basic-Operations#backwards-compatibility) in that doc too (not possible).

+1 on preventing accidental exposure of secrets in `Debug` output. I converted over from using a `HeaderValue` explicitly marked sensitive to the `Authorization` typed header and had expected that would...

Thanks @glommer and sorry about the bug @artemyarulin. I will try to take a look soon! Maybe this was a bad assumption `safe to borrow now across yield points as...

@AeroNotix I don't expect to be able to get around to this until the next weekend, am heading on vacation. Do you want to take a crack at it? Or...

made some progress on getting jepsen's elasticsearch test going (and producing a split-brain) ty @abailly for the vagrantization, really helps! i had some errors due to which i ended up...

yes, that's the approach I am going with current diff https://gist.github.com/shikhar/84945b975432bdf385ef

using eskka: ``` {:valid? true, :html {:valid? true}, :set {:valid? true, :lost "#{}", :recovered "#{267..268 270..273 275 278..279 286..287 289..292 294..296 299 301..302 306..308 310 312..314 317 319..320 323..325 327..329...

@AeroNotix just pushed it here https://github.com/shikhar/jepsen/tree/eskka you run it the same way as the ES tests since I updated `elasticsearch_test.clj` & `elasticsearch.clj` in place

In the interest of disclosure, seen some recent failures with a small number of writes lost using various partitioner strategies specified in `nemesis.clj`. Digging into them.

As I mentioned [here](http://aphyr.com/posts/317-call-me-maybe-elasticsearch#comments), I think the current failures are related to other bugs in ES that are hopefully going to be tackled in https://github.com/elasticsearch/elasticsearch/tree/feature/improve_zen. Here are the latest results...