Download and install Scylla Open Source on Docker, AWS, RHEL 7, CentOS 7, Debian, Virtual Box, Ubuntu or compile the source from GitHub.
Need premium features? Scylla Enterprise includes a Scylla Enterprise license, tested and certified binaries, cluster administration and task automation, hot fixes, 24/7 technical support, and more. SCYLLA ENTERPRISE 
Running Scylla in Docker is the simplest way to experiment with Scylla and we highly recommend it. However, running stateful containers is complex and tuning is needed to maximize the performance. We recommend that you use packages and follow Best Practices for Running Scylla on Docker.
$ docker run --name scylla -d scylladb/scylla$ docker run --name scylla-node2 -d scylladb/scylla --seeds="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' scylla)"$ docker run --name scylla-node3 -d scylladb/scylla --seeds="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' scylla)"$ docker exec -it scylla nodetool statusDatacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN 172.17.0.3 357 KB 256 66.4% 76ca991f-cf38-4984-8991-7675721a8bf8 rack1
UN 172.17.0.2 354.12 KB 256 70.6% dca727dd-c564-4166-b48f-ac79a5153503 rack1
UN 172.17.0.4 343.46 KB 256 63.0% 0f6d6b2e-de41-4729-a6a6-77e6f228fc5c rack1
$ docker exec -it scylla cqlshConnected to Test Cluster at 172.17.0.2:9042.
[cqlsh 5.0.1 | Cassandra 2.1.8 | CQL spec 3.2.1 | Native protocol v3]
Use HELP for help.
cqlsh>
Visit Scylla Documentation to get best practices for running Scylla on Docker.
For bug reports, please use Scylla’s issue tracker on GitHub. Please read the How to report a Scylla problem page before you report bugs. For general help, see Scylla’s documentation. For questions and comments, use Scylla’s mailing lists.
Scylla Community AMI is optimized for i3 instances with zero tuning and maximum performance.
Note that the Scylla AMIs will not work without an attached drive(s) for XFS.
EU West 1 (Ireland)
eu-west-1
ami-077d2151034a71550
Scylla 3.0.0 AMI
South America (São Paulo)
sa-east-1
ami-0efb06298dc4f709a
Scylla 3.0.0 AMI
For a production system, instances with a fast network and large SSD are recommended. The following instance is pre-tuned in the Scylla AMI and recommended for highest performance:
Other instance types will work, but with lesser permanence. If you do choose such a type, make sure to run scylla_setup, and answer Yes to “Do you want to setup IO configuration?” prompt.
| Option | Description |
| clustername | Required. The name of the cluster. |
| totalnodes | Required. The number of nodes you are adding to cluster. Use the same value as the “Number of instances” above. |
| seeds | Optional. An ip address of a node in an existing cluster. This will instruct Scylla to join an existing cluster. The “clustername” option must match that of the existing cluster. |
| stop-services | Optional. Do not start Scylla service on the nodes |
Example:
--clustername test-cluster
--totalnodes 3
Scylla AMI require XFS to work. You Must attach at least one drive for Scylla to use as XFS for the data directory. When attaching more than one drive, AMI setup will install RAID0 on all of them.
The Scylla AMI requires at least two instance store volumes. The Scylla data directory will be formatted with XFS when the instance first boots. Scylla will fail to start if only one volume is configured.
Make sure all Scylla Ports are open.
Launch! You now have a running Scylla cluster on EC2.
To connect to the servers, use the username centos.
ssh -i your-key-pair.pem centos@ec2-public-ipDefault file paths:
/etc/scylla/scylla.yaml/var/lib/scylla/To check that the Scylla server and the JMX component are running, run nodetool.
nodetool statusNote: This Scylla AMI does not support automatic multi-zone deployment.
It is highly recommended to have a Scylla monitoring stack in place. For more on how to setup Scylla monitoring with Grafana here
Scylla servers set up using this method have the system configuration covered on System Configuration Guide already applied. See the guide for a complete reference on settings used.
Scylla offers binaries ready for install on RHEL 7, CentOS 7, Debian and Ubuntu. To download, please register and a link to the appropriate repo will be emailed to you.
We ask you to register for binary downloads so we can help you be as successful as possible and let you know about patches and fixes, learning resources, new features, and capabilities. We also invite you to share your feedback to help us improve Scylla.
Please visit the Scylla GitHub repository for the most up to date instructions.
git clone https://github.com/scylladb/scylla.gitcd scylla
git submodule update --init --recursive
sudo ./install-dependencies.sh
./configure.py --mode=release
ninja-build
./build/release/scylla
./build/release/scylla --datadir tmp --commitlog-directory tmp --smp 1./build/release/scylla --help
For more information on building Scylla, please visit the HACKING page on the GitHub repository.
For bug reports, please use Scylla’s issue tracker on GitHub. Please read the How to report a Scylla problem page before you report bugs. For general help, see Scylla’s documentation. For questions and comments, use Scylla’s mailing lists.
Deploying Scylla in a VirtualBox instance is a good starting point for testing functionality and compatibility, and for local development and integration testing of applications using Scylla. Please note: Deploying Scylla in VirtualBox is not recommended or supported for production. The performance benefits of Scylla may not be visible on VirtualBox.
If you don’t have Internet connectivity from your VirtualBox instance, you will need to bring up a network interface.
Go to the network configuration directory
cd /etc/sysconfig/network-scripts/
Check for ifcfg scripts available. They will be named with the name of the Ethernet interface. You’ll have one named ifcfg-enp0s3, or similar.
Activate the connectivity, with
ifup ifcfg-enp0s3
To make the connection permanent in the next boot, open the configuration file with your preferred editor and make sure the setting is: ONBOOT=yes
Define forwarding ports in the NAT configuration in VirtualBox network settings: Check your network settings and define port forwarding as described below: Machine→ Settings → Network→ Port Forwarding
Set the forwarding ports for Scylla: 9042, 7000, 7001, 9180 and 7199
firewall-cmd or iptables.In CentOS 7 you can use the firewall-cmd utility.
firewall-cmd --zone=public --add-port=9042/tcp --permanent
firewall-cmd --reload
Or, in other configurations, you can use the iptables command.
iptables -I INPUT -p tcp --dport 9042 -j ACCEPT
service iptables save
scylla.yaml file, which can be found in the /etc/scylla/ directory.listen_address: 10.0.2.15
rpc_address: 10.0.2.15
- seeds: "10.0.2.15"
scylla_setup
systemctl start scylla-servercqlsh
cqlsh> describe keyspaces;
system_traces system_schema system_auth system
cqlsh>
Scyllas-MacBook-Pro:bin scylla$ ./cqlsh 127.0.0.1
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.8 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh>
Running Scylla in Docker is the simplest way to experiment with Scylla and we highly recommend it. However, running stateful containers is complex and tuning is needed to maximize the performance. We recommend that you use packages and follow Best Practices for Running Scylla on Docker.
$ docker run --name scylla -d scylladb/scylla$ docker run --name scylla-node2 -d scylladb/scylla --seeds="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' scylla)"$ docker run --name scylla-node3 -d scylladb/scylla --seeds="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' scylla)"$ docker exec -it scylla nodetool statusDatacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN 172.17.0.3 357 KB 256 66.4% 76ca991f-cf38-4984-8991-7675721a8bf8 rack1
UN 172.17.0.2 354.12 KB 256 70.6% dca727dd-c564-4166-b48f-ac79a5153503 rack1
UN 172.17.0.4 343.46 KB 256 63.0% 0f6d6b2e-de41-4729-a6a6-77e6f228fc5c rack1
$ docker exec -it scylla cqlshConnected to Test Cluster at 172.17.0.2:9042.
[cqlsh 5.0.1 | Cassandra 2.1.8 | CQL spec 3.2.1 | Native protocol v3]
Use HELP for help.
cqlsh>
Visit Scylla Documentation to get best practices for running Scylla on Docker.
For bug reports, please use Scylla’s issue tracker on GitHub. Please read the How to report a Scylla problem page before you report bugs. For general help, see Scylla’s documentation. For questions and comments, use Scylla’s mailing lists.
Scylla Community AMI is optimized for i3 instances with zero tuning and maximum performance.
Note that the Scylla AMIs will not work without an attached drive(s) for XFS.
EU West 1 (Ireland)
eu-west-1
ami-077d2151034a71550
Scylla 3.0.0 AMI
South America (São Paulo)
sa-east-1
ami-0efb06298dc4f709a
Scylla 3.0.0 AMI
For a production system, instances with a fast network and large SSD are recommended. The following instance is pre-tuned in the Scylla AMI and recommended for highest performance:
Other instance types will work, but with lesser permanence. If you do choose such a type, make sure to run scylla_setup, and answer Yes to “Do you want to setup IO configuration?” prompt.
| Option | Description |
| clustername | Required. The name of the cluster. |
| totalnodes | Required. The number of nodes you are adding to cluster. Use the same value as the “Number of instances” above. |
| seeds | Optional. An ip address of a node in an existing cluster. This will instruct Scylla to join an existing cluster. The “clustername” option must match that of the existing cluster. |
| stop-services | Optional. Do not start Scylla service on the nodes |
Example:
--clustername test-cluster
--totalnodes 3
Scylla AMI require XFS to work. You Must attach at least one drive for Scylla to use as XFS for the data directory. When attaching more than one drive, AMI setup will install RAID0 on all of them.
The Scylla AMI requires at least two instance store volumes. The Scylla data directory will be formatted with XFS when the instance first boots. Scylla will fail to start if only one volume is configured.
Make sure all Scylla Ports are open.
Launch! You now have a running Scylla cluster on EC2.
To connect to the servers, use the username centos.
ssh -i your-key-pair.pem centos@ec2-public-ipDefault file paths:
/etc/scylla/scylla.yaml/var/lib/scylla/To check that the Scylla server and the JMX component are running, run nodetool.
nodetool statusNote: This Scylla AMI does not support automatic multi-zone deployment.
It is highly recommended to have a Scylla monitoring stack in place. For more on how to setup Scylla monitoring with Grafana here
Scylla servers set up using this method have the system configuration covered on System Configuration Guide already applied. See the guide for a complete reference on settings used.
Scylla offers binaries ready for install on RHEL 7, CentOS 7, Debian and Ubuntu. To download, please register and a link to the appropriate repo will be emailed to you.
We ask you to register for binary downloads so we can help you be as successful as possible and let you know about patches and fixes, learning resources, new features, and capabilities. We also invite you to share your feedback to help us improve Scylla.
Please visit the Scylla GitHub repository for the most up to date instructions.
git clone https://github.com/scylladb/scylla.gitcd scylla
git submodule update --init --recursive
sudo ./install-dependencies.sh
./configure.py --mode=release
ninja-build
./build/release/scylla
./build/release/scylla --datadir tmp --commitlog-directory tmp --smp 1./build/release/scylla --help
For more information on building Scylla, please visit the HACKING page on the GitHub repository.
For bug reports, please use Scylla’s issue tracker on GitHub. Please read the How to report a Scylla problem page before you report bugs. For general help, see Scylla’s documentation. For questions and comments, use Scylla’s mailing lists.
Deploying Scylla in a VirtualBox instance is a good starting point for testing functionality and compatibility, and for local development and integration testing of applications using Scylla. Please note: Deploying Scylla in VirtualBox is not recommended or supported for production. The performance benefits of Scylla may not be visible on VirtualBox.
If you don’t have Internet connectivity from your VirtualBox instance, you will need to bring up a network interface.
Go to the network configuration directory
cd /etc/sysconfig/network-scripts/
Check for ifcfg scripts available. They will be named with the name of the Ethernet interface. You’ll have one named ifcfg-enp0s3, or similar.
Activate the connectivity, with
ifup ifcfg-enp0s3
To make the connection permanent in the next boot, open the configuration file with your preferred editor and make sure the setting is: ONBOOT=yes
Define forwarding ports in the NAT configuration in VirtualBox network settings: Check your network settings and define port forwarding as described below: Machine→ Settings → Network→ Port Forwarding
Set the forwarding ports for Scylla: 9042, 7000, 7001, 9180 and 7199
firewall-cmd or iptables.In CentOS 7 you can use the firewall-cmd utility.
firewall-cmd --zone=public --add-port=9042/tcp --permanent
firewall-cmd --reload
Or, in other configurations, you can use the iptables command.
iptables -I INPUT -p tcp --dport 9042 -j ACCEPT
service iptables save
scylla.yaml file, which can be found in the /etc/scylla/ directory.listen_address: 10.0.2.15
rpc_address: 10.0.2.15
- seeds: "10.0.2.15"
scylla_setup
systemctl start scylla-servercqlsh
cqlsh> describe keyspaces;
system_traces system_schema system_auth system
cqlsh>
Scyllas-MacBook-Pro:bin scylla$ ./cqlsh 127.0.0.1
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.8 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh>
Terms of Use Privacy Policy ©ScyllaDB 2019
Apache®, Apache Cassandra®, are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. No endorsement by The Apache Software Foundation is implied by the use of these marks.
