Note that the Scylla AMIs will not work without an attached drive(s) for XFS.
|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|
--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.
Launch! You now have a running Scylla cluster on EC2.
To connect to the servers, use the username
ssh -i your-key-pair.pem centos@ec2-public-ip
Default file paths:
To check that the Scylla server and the JMX component are running, run
Note: 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.
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.