Backport the following improvements for test.py topology tests for CI stability: - https://github.com/scylladb/scylladb/pull/12652 - https://github.com/scylladb/scylladb/pull/12630 - https://github.com/scylladb/scylladb/pull/12619 - https://github.com/scylladb/scylladb/pull/12686 - picked from https://github.com/scylladb/scylladb/pull/12726:9ceb6aba81- picked from https://github.com/scylladb/scylladb/pull/12173:fc60484422- https://github.com/scylladb/scylladb/pull/12765 - https://github.com/scylladb/scylladb/pull/12804 - https://github.com/scylladb/scylladb/pull/13342 - https://github.com/scylladb/scylladb/pull/13589 - picked from https://github.com/scylladb/scylladb/pull/13135:7309a1bd6b- picked from https://github.com/scylladb/scylladb/pull/13134:21b505e67c,a4411e9ec4,c1d0ee2bce,8e3392c64f,794d0e4000,e407956e9f- https://github.com/scylladb/scylladb/pull/13271 - https://github.com/scylladb/scylladb/pull/13399 - picked from https://github.com/scylladb/scylladb/pull/12699:3508a4e41e,08d754e13f,62a945ccd5,041ee3ffdd- https://github.com/scylladb/scylladb/pull/13438 (but skipped the test_mutation_schema_change.py fix since I didn't backport this new test) - https://github.com/scylladb/scylladb/pull/13427 - https://github.com/scylladb/scylladb/pull/13756 - https://github.com/scylladb/scylladb/pull/13789 - https://github.com/scylladb/scylladb/pull/13933 (but skipped the test_snapshot.py fix since I didn't backport this new test) Closes #14215 * github.com:scylladb/scylladb: test: pylib: fix `read_barrier` implementation test: pylib: random_tables: perform read barrier in `verify_schema` test: issue a read barrier before checking ring consistency Merge 'scylla_cluster.py: fix read_last_line' from Gusev Petr test/pylib: ManagerClient helpers to wait for... test: pylib: Add a way to create cql connections with particular coordinators test/pylib: get gossiper alive endpoints test/topology: default replication factor 3 test/pylib: configurable replication factor scylla_cluster.py: optimize node logs reading test/pylib: RandomTables.add_column with value column scylla_cluster.py: add start flag to server_add ServerInfo: drop host_id scylla_cluster.py: add config to server_add scylla_cluster.py: add expected_error to server_start scylla_cluster.py: ScyllaServer.start, refactor error reporting scylla_cluster.py: fix ScyllaServer.start, reset cmd if start failed test: improve logging in ScyllaCluster test: topology smp test with custom cluster test/pylib: topology: support clusters of initial size 0 Merge 'test/pylib: split and refactor topology tests' from Alecco Merge 'test/pylib: use larger timeout for decommission/removenode' from Kamil Braun test: Increase START_TIMEOUT test/pylib: one-shot error injection helper test: topology: wait for token ring/group 0 consistency after decommission test: topology: verify that group 0 and token ring are consistent Merge 'pytest: start after ungraceful stop' from Alecco Merge 'test.py: improve test failure handling' from Kamil Braun
Scylla
What is Scylla?
Scylla is the real-time big data database that is API-compatible with Apache Cassandra and Amazon DynamoDB. Scylla embraces a shared-nothing approach that increases throughput and storage capacity to realize order-of-magnitude performance improvements and reduce hardware costs.
For more information, please see the ScyllaDB web site.
Build Prerequisites
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 Scylla
Building Scylla with the frozen toolchain dbuild is as easy as:
$ git submodule update --init --force --recursive
$ ./tools/toolchain/dbuild ./configure.py
$ ./tools/toolchain/dbuild ninja build/release/scylla
For further information, please see:
- Developer documentation for more information on building Scylla.
- Build documentation on how to build Scylla binaries, tests, and packages.
- Docker image build documentation for information on how to build Docker images.
Running Scylla
To start Scylla server, run:
$ ./tools/toolchain/dbuild ./build/release/scylla --workdir tmp --smp 1 --developer-mode 1
This will start a Scylla node with one CPU core allocated to it and data files stored in the tmp directory.
The --developer-mode is needed to disable the various checks Scylla performs at startup to ensure the machine is configured for maximum performance (not relevant on development workstations).
Please note that you need to run Scylla with dbuild if you built it with the frozen toolchain.
For more run options, run:
$ ./tools/toolchain/dbuild ./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 support for the API of Amazon DynamoDB™, which needs to be enabled and configured in order to be used. For more information on how to enable the DynamoDB™ API in Scylla, and the current compatibility of this feature as well as Scylla-specific extensions, see Alternator and Getting started with Alternator.
Documentation
Documentation can be found here. 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.
Contributing to Scylla
If you want to report a bug or submit a pull request or a patch, please read the contribution guidelines.
If you are a developer working on Scylla, please read the developer guidelines.
Contact
- The users mailing list and Slack channel are for users to discuss configuration, management, and operations of the ScyllaDB open source.
- The developers mailing list is for developers and people interested in following the development of ScyllaDB to discuss technical topics.