Skip to content
#

distributed-database

Here are 248 public repositories matching this topic...

cockroach
knz
knz commented Nov 1, 2021

Forked from #72227 (initially reported by @amitsadaphule )

Describe the problem

The expected output in the test TestAnonymizeStatementsForReporting (conn_executor_test.go) is overly prescriptive as to the result of formatting an error containing a redacted statement.

Namely, it has particular requirements about how the stack trace is formatted.

This is unnecessary for the test, w

sfc-gh-ajbeamon
sfc-gh-ajbeamon commented Nov 29, 2021

We create a number of threads in various places in our code, and in most cases we do not give these threads names. It could be helpful to have names that make it easier for us to see what a thread is doing. Some examples include:

  1. The network thread created by bindings (some bindings name this thread, others do not)
  2. External network threads (name proposed in #6033)
  3. Trace logging threa
yugabyte-db
sanketkedia
sanketkedia commented Nov 2, 2021

Description

Currently, for e.g. say that out of 3 copies of a tablet, we want to have 2 copies in C1.R1.Z1 and 1 copy in C2.R2.Z2 then we would specify it as below:

./bin/yb-admin \
    -master_addresses $MASTER_RPC_ADDRS \
    modify_placement_info  \
    C1.R1.Z1,C1.R1.Z1,C2.R2.Z2 3

However, this is somewhat complex and hard to follow. We don't need to necessarily r

Improve this page

Add a description, image, and links to the distributed-database topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the distributed-database topic, visit your repo's landing page and select "manage topics."

Learn more