scylladb/scylladb

Scylla causes 'memory per shard too low' on <2GB RAM EC2 instance-type

Open

#2,630 opened on Jul 25, 2017

View on GitHub
 (10 comments) (0 reactions) (0 assignees)C++ (1,169 forks)batch import
good_first_issue

Repository metrics

Stars
 (11,972 stars)
PR merge metrics
 (Avg merge 20d 8h) (109 merged PRs in 30d)

Description

It seems we are not able to run our AMI on t2.micro(1GB RAM) / t2.small(2GB RAM).

Installation details Scylla version (or git commit hash): 1.7.3 Cluster size: OS (RHEL/CentOS/Ubuntu/AWS AMI): AWS AMI

Jul 25 09:20:19 ip-172-16-99-91 scylla[2192]: Scylla version 1.7.3-0.20170719.41b4055 starting ...
Jul 25 09:20:19 ip-172-16-99-91 scylla[2192]:  [shard 0] init - Only 476 MiB per shard; this is below the recommended minimum of 1 GiB/shard; terminating.Configure more memory (--memory option) or decrease shard count (--smp option).
Jul 25 09:20:19 ip-172-16-99-91 scylla[2192]:  [shard 0] seastar - Exiting on unhandled exception: std::runtime_error (configuration (memory per shard too low))
Jul 25 09:20:20 ip-172-16-99-91 systemd[1]: scylla-server.service: main process exited, code=exited, status=1/FAILURE

Contributor guide