It is mentioned that there is an error code page for v2 protocol:
https://github.com/etcd-io/etcd/blob/ae7862e8bc8007eb396099db4e0e04ac026c8df5/server/etcdserver/api/v2error/error.go#L16

However, I can't find Documentation/v2/errorcode.md in this repo. Is the comment stale?

Informs #56536

Use of external storage temp tokens, together with explicit authentication is dangerous.
In general, explicitly specified tokens could expire while long running operation (backup, restore)
is still executing, without any way for us to regenerate such temp token.

We should error out if external storage URI uses temporary credentials for backup, restore,
import, scheduled ba

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

Background

Considering the check-style for functions,
public ASTNode visitQuerySpecification(final QuerySpecificationContext ctx) is expected rather than
public ASTNode visitQuerySpecification(final MySQLStatementParser.QuerySpecificationContext ctx).

Hence, this issue aims to correct the nonstandard visit function check-style.

How?

1. Enter into directory `~/sh

This issue is the umbrella issue tracking the effort to add namespace to FDB code base. Idea is that with namespace in place, code would be much easier to read and understand at the call site. The coupling between different parts of the system would be easier to be seen and understood. Also this can help with potential symbol collisions.

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-

For commands that stop processes (e.g. destroy, stop, stop_node, restart), add a -f/--force flag that kills them with SIGKILL. This is in response to the recent regression that caused yb-ctl to be unable to stop postgres processes. For developers, we need to manually kill the processes each time (or write a script ourselves). Having this built into yb-ctl will help for now and o

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

Seeing the following exception which ends up being classified as an INTERNAL_ERROR instead of a USER_ERROR:

java.time.DateTimeException: Invalid value for HourOfDay (valid values 0 - 23): 24
	at java.base/java.time.temporal.ValueRange.checkValidValue(ValueRange.java:311)
	at java.base/java.time.temporal.ChronoField.checkValidValue(ChronoField.java:717)
	at java.base/java.time

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