I'm using TLS on etcd 3.3.12 and have a mix of etcd proxies and masters. The proxies don't seem to honour the --cipher-suites setting, as it ends up with ECDHE-RSA-AES256-GCM-SHA384 despite --cipher-suites=TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 being set.

$ pgrep -laf /usr/bin/etcd
21968 /usr/bin/etcd --listen-client-urls https://0.0.0.0:4000 --adv

Bug Report

What version of TiKV are you using?

I think the description of config max-tasks-per-worker-high in the document is wrong:https://github.com/tikv/tikv/blob/master/docs/V2.1/op-guide/coprocessor-config.md#max-tasks-per-worker-high
https://github.com/tikv/tikv/blob/master/docs/refer

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

Hey!
Not a big problem of course but currently when you do "pip install patroni" you still need to go to Github and save a copy of for https://github.com/zalando/patroni/blob/master/postgres0.yml to get started. I know there are env variables but there are quite some to remember. So would be very convenient if running something like "patroni --initconf postgres0.yml" would fill the postgres0.yml

1. create an edgetype with prop

> create edge choose(grade int)

2. create the edgetype without any prop using if not exists

> create edge if not exists choose()
Execution succeeded (Time spent: 12.129/13.466 ms)

3. check the schema of choose

describe edge choose;
================
| Field | Type |
================
| grade | int  |
----------------
G

Looks like the error code in braft::Status is mapped as error codes in the C++ standard. For example, I saw this in closure_queue.cpp:

(*it)->status().set_error(EPERM, "leader stepped down");

Similar logic is scattered around the code base.

I am wondering whether we have any documentation for all the possible error codes (i.e. the mapping)?

Is your feature request related to a problem? Please describe.

Configuration options are not documented on the web site.

Describe the solution you'd like

I need to look at the code (i.e. the *Config classes) or at the Javadoc in order to determine the configuration options. I'd like to have it documented on the website and to be sure that the configuration options match whatever

I see that @siddontang added a Jepsen test for LogCabin a few months ago. It uses the CLI client. jepsen-io/jepsen@90720bf

@siddontang: What's the state of this test? Did you find anything when you ran it? What'd you learn? What's next?

Should we add a mention of this in the LogCabin README? Make it part of the release process?

The leadership changes section made me nervous because it looks like there is some reliance on the nodes perceived Raft status (which may not be the Raft status). I traced the code and indeed on proposal, the node's local Raft status is determined to decide whether that node is the leader or not. During network partitions however, a node ma

Expected result:

Can't find schema.json or it's not readable. Default location (`./etc/schema.json`) could be overridden with `-s, --schema-file` command-line paramethers

Actual result:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1084:5
note: run with `RUST_

Async/await is on the path to stable, and is much clearer to read and write than raw futures. Tokio is also working on futures 0.3 native support, so it would be great to use async/await and futures 0.3 in Raft.

I have a use-case where two key-val should be inserted atomically (if not exist)and either insert fails should roll back. The 2nd key is a secondary index.

Key1= Hash1
Value1= Token1

Key2= Token1
Value2= json payload

How can I insert both atomically? Now if Key1 or Key2 (Token1) already exists, it should roll back the operation.

I see [HmsetWithTxn ](https://github.com/yongman

Now, some query examples(simple and prefix) are given, but it seems to be not enough to get quick start for more complicated query logic.

Query String Query supports all kinds of query such as Phrases, Field Scoping, Boolean Query, Numeric Ranges, fuzzy search and so on.

If more examples are given, it seems to be more friendly to tiro.

I'm confused about the example for data migration during code updates. The runMigration example function asserts that this is an upgrade from version 0 to version 1. Shouldn't this be from version 1 to version 2? Or am I completely misunderstanding how migrations work?