![install cqlsh for cassandra 2.1 mac install cqlsh for cassandra 2.1 mac](https://image.slidesharecdn.com/deepdiveintocassandra-150310084213-conversion-gate01/95/deep-dive-into-cassandra-9-638.jpg)
The change was implemented in Cassandra version 3.2. One notable change which modified how Cassandra uses the data_file_directories setting was CASSANDRA-6696. Mc-6-big-Data.db mc-6-big-Index.db mc-6-big-TOC.txt Mc-6-big-CompressionInfo.db mc-6-big-Filter.db mc-6-big-Summary.db Mc-5-big-Data.db mc-5-big-Index.db mc-5-big-TOC.txt Mc-5-big-CompressionInfo.db mc-5-big-Filter.db mc-5-big-Summary.db To use it just specify the list of directories you want Cassandra to use for data storage. The data_file_directories feature is fairly straight forward in that it allows Cassandra to use multiple directories to store data. For now I will leave the details of the setting alone, so we can focus exclusively on the data_file_directories setting.
![install cqlsh for cassandra 2.1 mac install cqlsh for cassandra 2.1 mac](http://4.bp.blogspot.com/-_g2cwnelt4U/U3bR-aCek3I/AAAAAAAAFaQ/l0EaNDP2cmQ/s1600/creatingCassandraKeyspace.png)
In relation to this setting, Cassandra also allows its behaviour on disk failure to be controlled using the disk_failure_policy setting. In Cassandra this feature is controlled by the data_file_directories setting in the cassandra.yaml file. The feature which allows Cassandra to store data on multiple disks is commonly referred to as JBOD which stands for “Just a Bunch Of Disks/Drives”. In this post we will go through some fine print when configuring Cassandra to use multiple disks. Recently I was working on a cluster and saw how this feature has the potential to silently cause problems in a cluster. This feature can help increase cluster capacity or prevent a node from running out space if bootstrapping a new one will take too long to complete. One of the longest lived features in Cassandra is the ability to allow a node to store data on more than one than one directory or disk.