Today, etcdctl endpoint health only performs a quorum GET. If server is corrupted or exceeded quota (which put the server into read only mode), this command incorrectly returns healthy.

Requesting to add support for \connect database similar to psql format, to be used in addition to how USE database is currently used in CRDB.

Now insert and query share the resource ( Max Process Count control) 。 When the query with high TPS，the insert will get error (“error: too many process”). I think separator the resource for Insert and Query will makes sense. Ensure enough resource for insert。It looks like Use Yarn， Insert and Query use the different resource quota。
Or the simple way , Can we set Ratio for Insert and

The old restore supports adding prefix and suffix to the backup data. This allows us to restore a key space (say [a, b)) to a new key space (say [awesome_a, awesome_b).

This feature is useful in:

• Performance testing: We do not want to throw away existing loaded data in the cluster because loading a huge DB takes time;
• Cross-verification: Users may want to verify the restored data in the

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-

The current message ("There is no data to display") is misleading. At the minimum, this message should be changed to something like "Fetching the data, please wait". Ideally the implementation should be changed to improving the data load behavior.

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Related to https://stackoverflow.com/questions/64432527/how-to-intercept-mondodb-query-from-presto-connector

https://github.com/prestosql/presto/blob/80d88f9cd66125cf9ba8db06cd6e73d61104ef3a/presto-mongodb/src/main/java/io/prestosql/plugin/mongodb/MongoSession.java#L274-L303

Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)

Currently a cache node object consists of a Key, a Value and a TTL. We should also add a field specifying the type of the Value