Asias He 7f3eb8b4e8 repair: Handle dropped table in repair_range
In commit 12d929a5ae (repair: Add table_id
to row_level_repair), a call to find_column_family() was added in
repair_range. In case of the table is dropped, it will fail the
repair_range which in turn fails the bootstrap operation.

Tests: update_cluster_layout_tests.py:TestUpdateClusterLayout.simple_add_new_node_while_schema_changes_test
Fixes: #5942
2020-07-01 12:13:14 +03:00
2020-06-14 08:18:37 -07:00
2020-07-01 10:15:49 +03:00
2020-06-14 08:18:37 -07:00
2020-06-18 09:54:37 +03:00
2020-06-18 09:54:37 +03:00
2020-06-30 19:27:21 +03:00
2020-02-07 08:59:39 +01:00
2020-06-18 09:54:37 +03:00
2020-06-14 08:18:39 -07:00
2020-06-14 08:18:39 -07:00
2019-12-19 15:43:04 +02:00
2020-06-18 09:51:23 +03:00
2020-06-29 14:23:32 -03:00
2020-01-30 11:10:08 +01:00
2020-03-03 11:34:00 +01:00
2020-04-06 15:07:28 +03:00
2020-02-17 10:59:15 +01:00
2020-01-29 14:05:01 -08:00
2020-06-26 20:27:28 +03:00
2020-02-17 10:59:06 +01:00
2020-03-03 11:34:00 +01:00
2020-06-27 21:17:33 +03:00
2020-03-03 11:34:00 +01:00
2020-06-23 19:39:54 +03:00
2020-03-03 11:34:00 +01:00
2020-06-11 17:12:49 +03:00

Scylla

Quick-start

Scylla is fairly fussy about its build environment, requiring very recent versions of the C++20 compiler and of many libraries to build. The document HACKING.md includes detailed information on building and developing Scylla, but to get Scylla building quickly on (almost) any build machine, Scylla offers a frozen toolchain, This is a pre-configured Docker image which includes recent versions of all the required compilers, libraries and build tools. Using the frozen toolchain allows you to avoid changing anything in your build machine to meet Scylla's requirements - you just need to meet the frozen toolchain's prerequisites (mostly, Docker or Podman being available).

Building and running Scylla with the frozen toolchain is as easy as:

$ ./tools/toolchain/dbuild ./configure.py
$ ./tools/toolchain/dbuild ninja build/release/scylla
$ ./tools/toolchain/dbuild ./build/release/scylla --developer-mode 1

Running Scylla

  • Run Scylla
./build/release/scylla

  • run Scylla with one CPU and ./tmp as work directory
./build/release/scylla --workdir tmp --smp 1
  • For more run options:
./build/release/scylla --help

Testing

See test.py manual.

Scylla APIs and compatibility

By default, Scylla is compatible with Apache Cassandra and its APIs - CQL and Thrift. There is also experimental support for the API of Amazon DynamoDB, but being experimental it needs to be explicitly enabled to be used. For more information on how to enable the experimental DynamoDB compatibility in Scylla, and the current limitations of this feature, see Alternator and Getting started with Alternator.

Documentation

Documentation can be found in ./docs and on the wiki. There is currently no clear definition of what goes where, so when looking for something be sure to check both. Seastar documentation can be found here. User documentation can be found here.

Training

Training material and online courses can be found at Scylla University. The courses are free, self-paced and include hands-on examples. They cover a variety of topics including Scylla data modeling, administration, architecture, basic NoSQL concepts, using drivers for application development, Scylla setup, failover, compactions, multi-datacenters and how Scylla integrates with third-party applications.

Building a CentOS-based Docker image

Build a Docker image with:

cd dist/docker/redhat
docker build -t <image-name> .

This build is based on executables downloaded from downloads.scylladb.com, not on the executables built in this source directory. See further instructions in dist/docker/redhat/README.md to build a docker image from your own executables.

Run the image with:

docker run -p $(hostname -i):9042:9042 -i -t <image name>

Contributing to Scylla

Hacking howto Guidelines for contributing

Description
No description provided
Readme 503 MiB
Languages
C++ 72.1%
Python 26.7%
CMake 0.3%
GAP 0.3%
Shell 0.3%