Database Reference
In-Depth Information
* soft nofile 32768
* hard nofile 32768
root soft nofile 32768
root hard nofile 32768
* soft memlock unlimited
* hard memlock unlimited
root soft memlock unlimited
root hard memlock unlimited
* soft as unlimited
* hard as unlimited
root soft as unlimited
root hard as unlimited
* soft nproc 10240
# CentOS/Red Hat systems
On CentOS or RedHat systems, change the system limits from 1024 to 10240
in /etc/security/limits.d/90-nproc.conf.
change the
max_map_count
for the system. This is the maximum number of
memory map areas that a process may have. The default value for this field is
65536. Most applications won't use anything even close to this value. Depending
on your use case, Cassandra may use a lot more areas of memory than most ap-
plications. Doubling the default value should give you plenty of headroom.
Listing 10.7
sysctl
Update for
max_map_count
# sysctl -w vm.max_map_count = 131072
Summary
As with any complex system, there is a steep learning curve for understanding the
behavior of your Cassandra cluster. It is not sufficient to figure out how your sys-
tem performs under normal circumstances; you also need to know how it performs
under load. Using some or all of the tools and techniques covered in this chapter
will help you find and diagnose some of the more common issues when adminis-
tering a Cassandra cluster.
