SSTable is an abbreviation for Sorted String Table. It is the fundamental storage building block in few of the modern Log Structured Merge Tree(LSM) based distributed database systems and key-value stores. It is used in Cassandra, BigTable and other systems. SSTable stands for Sorted Strings Table which stores a set of immutable row fragments or partitions in sorted order based on row/partition keys. This article explains how the open source Cassandra defines the format of SSTable. Using the information in this article you can understand implementation of SSTable in other systems.
Cassandra creates a new SSTable when the data of a column family in Memtable is flushed to disk. SSTable files of a column family are stored in its respective column family directory. This article describes the format used for Thrift column family. Please check the latest post New Storage Format for the storage format changes in Cassandra 3.0 and the CQL Storage format post to understand how CQL Tables are stored in Cassandra 2.0.

The data in a SSTable is organized in six types of component files.  The format of a SSTable component file is
<keyspace>-<column family>-[tmp marker]-<version>-<generation>-<component>.db

<keyspace> and <column family> fields represent the Keyspace and column family of the SSTable, <version> is an alphabetic string which represents SSTable storage format version, <generation> is an index number which is incremented every time a new SSTable is created for a column family and <component> represents the type of information stored in the file. The optional "tmp" marker in the file name indicates that the file is still being created. The six SSTable components are Data, Index, Filter, Summary, CompressionInfo and Statistics.

For example, I created a column family data in Keyspace usertable using cassandra-cli and inserted 1000 rows {user0, user1,...user999} with Cassandra version 1.2.5.

create keyspace usertable with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:1};
use usertable;
create column family data with comparator=UTF8Type;

The SSTables under cassandra/data/usertable/data directory:


In the above SSTable listing, the SSTable storage format version is ic, generation number is 1. The usertable-data-ic-1-TOC.txt contains the list of components for the SSTable.

Data file stores the base data of SSTable which contains the set of rows and their columns. For each row, it stores the row key, data size, column names bloom filter, columns index, row level tombstone information, column count, and the list of columns.  The columns are stored in sorted order by their names. Filter file stores the row keys bloom filter.

Index file contains the SSTable Index which maps row keys to their respective offsets in the Data file. Row keys are stored in sorted order based on their tokens. Each row key is associated with an index entry which includes the position in the Data file where its data is stored. New versions of SSTable (version "ia" and above), promoted additional row level information from Data file to the index entry to improve performance for wide rows. A row's columns index, and its tombstone information are also included in its index entry. SSTable version "ic" also stores column names bloom filter in the index entry.

Summary file contains the index summary and index boundaries of the SSTable index. The index summary is calculated from SSTable index. It samples row indexes that are index_interval (Default index_interval is 128) apart with their respective positions in the index file. Index boundaries include the start and end row keys in the SSTable index.

CompressionInfo file stores compression metadata information that includes uncompressed data length, chuck size, and a list of the chunk offsets. Statistics file contains metadata for a SSTable. The metadata includes histograms for estimated row size and estimated column count. It also includes the partitioner used for distributing the key, the ratio of compressed data to uncompressed data and the list of SSTable generation numbers from which this SSTable is compacted. If a SSTable is created from Memtable flush then  the list of ancestor generation numbers will be empty.

All SSTable storage format versions and their respective Cassandra versions are described in and the different components are described in

SSTable data format (version "jb")

A column inside a row is stored as four parts. It begins with column name, followed by the type of the column, its creation time and column value. A column name is stored as two bytes indicating the length of the name followed by the name itself. The type is a one byte mask value indicating the type of stored column. Based on the column type remaining bytes of the column are processed.

Column timestamp is a eight bytes value indicating the column creation time. For a deleted column, the timestamp indicated the time when the column was deleted. Column value is stored as four bytes indicating the value size followed by the bytes storing the actual column value.

Version "ja"

In version "ja" SSTable format, Column names bloom filter, Column count fields  are removed from SSTable data component file. The fields, localDeletionTime and  markedForDeleteAt added to represent deletion timestamps of a row. For a row tombstone, localDeletionTime represents the  timestamp in seconds at which a top level tombstone is created and markedForDeleteAt represents a timestamp in microseconds after which the data in a row should be considered as deleted. The default value for localDeletionTime is 0x7fffffff and the default value for markedForDeleteAt is 0x8000000000000000. If a row's deletion timestamps contain the default values then it contains live data.

Row size field is also removed from data component file. A special 0 length column name is added to represent the end of row. Row size is calculated from Index file. Index file contains starting offsets of each row.  Successive offsets are used to calculate each row size except for the last row in SSTable. For the last row, end of data file is used to calculate its size.

Version "ka"

In version "ka", contents of Statistics component file is split in to 3 types of metadata called validation, compaction and stats. Validation metadata is used to validate SSTable which includes partitioner and bloom filter fp chance fields. Compaction metadata includes ancestors information which is also available in older formats and a new field called cardinality estimator. Cardinality estimator is used to efficiently pre-allocate bloom filter space in a merged compaction file by estimating how much the input SStables overlap. Stats metadata contains rest of the information available in old formats and two additional fields. First one is a flag to track the presence of local/remote counter shards and the other one is for storing the repair time. reads the rows and columns in a given SSTable and converts those to JSON format similar to sstable2json tool available in Cassandra distribution. It doesn't require access to Cassandra column families in system keyspace to decode SSTable data like sstable2json tool. It is tested with version "jb".
Other two important components of Cassandra storage architecture are Memtable and CommitLog which are described in following blog posts.


  1. Hello Sir,
    My name is kriti sharma.I am a student. I am totally new in cassandra. I have a little doubt in above blog what you wrote is ,that how did you inserted 1000 rows in cassandra table. or I can say how we can insert data >=1000 in cassandra tables?
    please reply as early as possible it's realy urgent for me.
    Thank you

    1. Hello Kriti,

      I used ycsb tool to load test data for my blog post. You can get it from

  2. Which files would be necessary during a restore? For example, the Summary file is not necessary as "The index summary is calculated from SSTable index."

    1. If sstable data is not compressed then Data component file is enough to restore all rows in it. Otherwise both Data and Compression component files are required to restore. Compression component file contains the offset of each compressed block in the data file.

      Index component file contains the offset in to the data file where each row's data starts. Using these offsets each row's size is calculated. But in the data file, a column name length 0 is added to mark end of row. End of row marker can be used to separate each row's data.

  3. The Data file does not hold a column names bloom filter anymore. See CASSANDRA-4885 for more details

    1. Thank you for the update. I originally used SSTable version "ic" for describing the format. Recently I included SSTable version "jb" also in this post. I will update it with this change.

  4. Dear, regarding to "Index file", you wrote: "Row keys are stored in sorted order"... but your figure does not look like that, right? Also, I checked an index file, it seems that row keys in the index file are not sorted.

    1. Hi Duong Mai,

      Thank you for your feedback. I think I didn't clearly explained it. In the index file the row keys are sorted based on their tokens not by their key names. I updated the text. Also I included a github link which includes a python script to read the index file.

  5. I have a question: Why does Cassandra keep all those components separately? As described in here "", InfluxDB's new storage engine keeps all components in a single file. Which is the better choice?

  6. In Cassandra case, at any point of time there can be more than one SSTable files for a column family. Each component file contains different types of information to find the right SSTables for a read query. The filter, summary and index component file contents are cached in memory to avoid extra disk seeks.

  7. Great post. Do you know how the storage format changed with the recent "ma" version of SSTable?

    1. In 3.0 release storage engine underneath changed to take advantage of CQL. I am planning to write a new blog post on the format used in 3.0 release

  8. Thanks for the post!

    Can we purge the history data by rolling shutdown cassandra->remove files older than certain date -> start instance again cross cluster nodes? Anything we have to pay more attention to this approach?


  9. hi have cassandra sstable file "mc" version i have used the python script from to view sstable file but its not working. Can you please let me know if this script support this version?