Skip to content
#

distributed-database

Here are 271 public repositories matching this topic...

mortehu
mortehu commented Mar 3, 2022

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

cockroach
sheaffej
sheaffej commented Mar 28, 2022

Please consider adding a way to control which nodes participate in an IMPORT operation so that nodes in far regions can be excluded from the import.

Consider a 3-region cluster, with nodes in: [Japan, US West, EU]. And let's import a table into a database that has only a primary region defined in US West. All of the table's replicas will be located in US West. And the CSV data to be imported is

C-enhancement A-bulkio good first issue T-bulkio
sfc-gh-ajbeamon
sfc-gh-ajbeamon commented Aug 9, 2021

Our CMake build process produces tarball packages using the cpack TGZ target. This produces a server and client package with a file layout meant to match where the various artifacts go.

Meanwhile, the packages we include on the download page are a flat archive of various binaries produced by the build process. This include one regular package and one debug package with debug symbols for a few

yugabyte-db
chrisckchang
chrisckchang commented Mar 16, 2022

Description

source: https://docs.yugabyte.com/latest/architecture/transactions/isolation-levels/#root

We begin the section by listing out 4 transaction isolation levels in decreasing order of strictness. Where possible, subsequent sections should follow this order to make it easier for readers to follow. For example, rewrite the second paragraph to read:

YugabyteDB supports three transa

good first issue area/documentation
jakekgrog
jakekgrog commented Jul 16, 2020

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

enhancement good first issue

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