Piotr Kołaczkowski

<p>Cassandra File System (CFS) is the default distributed file system in the DataStax Enterprise platform in versions 2.0 to 5.0. Its primary purpose is to support Hadoop and Spark workloads with temporary Hadoop-compatible storage. In DSE 5.1, CFS has been deprecated and replaced with a much improved DataStax Enterprise File System (DSEFS). DSEFS is available as an option in DSE 5.0, and was made the default distributed file system in DSE 5.1.</p>

<h2>A Brief History of CFS</h2>

<p>CFS stores file data in Apache Cassandra<sup>®</sup>. This allows for reuse of Cassandra features and offers scalability, high availability and great operational simplicity. Just as Cassandra is shared-nothing, CFS is shared-nothing as well. It scales linearly with the number of nodes in either performance and capacity.</p>

<p>Because Cassandra was not designed to store huge blobs of binary data as single cells, files in CFS have to be split into blocks and subblocks. Subblocks are each 2 MB large by default. A block is stored in a table partition. A subblock is stored in a table cell. The&nbsp;inodes&nbsp;table stores file metadata such as name and attributes and a list of block identifiers.</p>
<img alt="CFS Model" data-align="center" data-entity-type="file" data-entity-uuid="69f6fc62-7f49-46d2-8a88-bdf2ece653dd" src="https://www.datastax.com/sites/default/files/inline-images/CFSmodel.png" />
<p>Except for Cassandra, CFS has almost no server-side components. All the operations like looking up or creating files, splitting/merging subblocks, and data compression/decompression are performed by the client. Therefore to access CFS, the client needs thrift access to Cassandra.</p>

<h2>CFS Limitations</h2>

<p>Unfortunately this design comes with a few limitations:</p>

<ul>
	<li>A subblock must be fully loaded into memory and transferred between the client and the storage before the operation timeout happens. This increases memory use.</li>
	<li>When writing to Cassandra, each row has to be written at least twice - for the first time to the commit log, and for the second time to a new sstable on disk.</li>
	<li>There is additional I/O overhead of Cassandra compaction, particularly for write-heavy workloads.</li>
	<li>Reclaiming space after deleting files is deferred until compaction. This can get particularly bad when dealing with workloads that cause writing temporary files, e.g. when doing exploratory analytics with Spark. When&nbsp;SizeTieredCompactionStrategy&nbsp;is used, this can result in taking several times more space than needed.</li>
	<li>Authorization is weak, because it is implemented on the client-side. The server administrator can only restrict who may and who may not access CFS at all, but it is not possible to restrict access to a part of the directory tree.</li>
</ul>

<p>To alleviate the delayed delete problem and reduce both the time and space overhead of compaction,&nbsp;CfsCompactionStrategy&nbsp;was introduced in DSE 2.1. This strategy flushes each block to a separate sstable. When the file needs to be deleted, it just deletes the right sstables from disk. It also doesn't waste I/O for repeatedly rewriting sstables. This is much faster and more efficient for short-lived files than reading and compacting sstables together, however in practice it introduces another set of problems. While there is no hard limit on the number of sstables in the keyspace, each sstable comes at some cost of used resources like file descriptors and memory. Too many sstables make it slow to find data and blow up some internal Cassandra structures like interval trees. It is very easy to run into issues by having too many small files. Simply put,&nbsp;CfsCompactionStrategy&nbsp;didn't scale in the general case, so it has been deprecated and removed in DSE 5.0.</p>

<h2>Introducing DSEFS</h2>

<p>DSEFS is the new default distributed file system in DSE 5.1. DSEFS is not just an evolution of CFS. DSEFS has been architected from scratch to address the shortcomings of CFS, as well as HDFS.</p>

<p>DSEFS supports all features of CFS and covers the basic subset of HDFS and WebHDFS APIs to enable seamless integration with Apache Spark and other tools that can work with HDFS. It also comes with a few unique features. Notable features include:</p>

<ul>
	<li>creating, listing, moving, renaming, deleting files and directories</li>
	<li>optional password / token authentication and kerberos authentication in Spark</li>
	<li>POSIX permissions and file attributes</li>
	<li>interactive console with access to DSEFS, local file system, CFS and other HDFS-compatible filesystems</li>
	<li>querying block locations for efficient data local processing in Spark or Hadoop</li>
	<li>replication and block size control</li>
	<li>transparent optional LZ4 compression</li>
	<li>a utility to check filesystem integrity (fsck)</li>
	<li>a utility to view status of the cluster (e.g. disk usage)</li>
</ul>

<h2>DSEFS Interactive Console</h2>

<p>DSEFS comes with a new console that speeds up interacting with remote filesystems. Previously, to access CFS, you had to launchdse hadoop fs&nbsp;command which started a new JVM, loaded required classes, then connected to the server and finally executed the requested command. Launching and connecting was repeated for every single command and could take a few seconds every time. DSEFS console can be launched only once and then can execute many commands reusing the same connection. It also understands a concept of working directory, so you don't need to type full remote paths with every command. You can use many file systems like DSEFS, CFS, HDFS, local file system in a single session. Tab-completion of paths helps to improve interaction speed even more.</p>
<img alt="Dsefs Shell" data-align="center" data-entity-type="file" data-entity-uuid="e9d4da8e-85a4-418c-8157-20cc1f740879" src="https://www.datastax.com/sites/default/files/inline-images/dsefs_shell.png" />
<h2>DSEFS Architecture</h2>

<p>The major difference between CFS and DSEFS architectures is that in DSEFS the data storage layer is separate from the metadata storage layer. Metadata, which includes information about paths, file names, file attributes, as well as pointers to data, are stored in Cassandra tables. File data are stored outside Cassandra, directly in the node's local file system. Data is split into blocks, each 64 MB large by default, and each block is stored in its own file.</p>
<img alt="Client Applications" data-align="center" data-entity-type="file" data-entity-uuid="ca2a3779-07af-42c0-9504-f11f860643c2" src="https://www.datastax.com/sites/default/files/inline-images/s9BaKXcczIG_YYBY9uts8Jg.png" />
<p>Storing data blocks in the local file system has several advantages:</p>

<ul>
	<li>There is virtually no limit on the number of blocks that can be stored, other than the capacity of storage devices installed in the cluster. Blocks at rest do not take any other system resources such as memory or file descriptors.</li>
	<li>The DSEFS server can stream a data block over the network very efficiently using&nbsp;sendfile&nbsp;without copying any part of it to JVM heap nor userspace memory.</li>
	<li>Writing data to blocks skips the Cassandra commit log, so every block needs to be written only once.</li>
	<li>Deleting files is fast and space is reclaimed immediately. Each block is stored in its own file in some storage directory, so deleting a file from DSEFS is just deleting files from the local file system. There is no need to wait for a compaction operation.</li>
	<li>Looking up blocks is faster than accessing sstables. Blocks can be quickly accessed directly by their name which is stored in the metadata.</li>
	<li>Replication for data can be configured in a very fine grained way, separately from Cassandra replication. For example files in one directory can have RF=3 and files in another directory can have RF=5. You can also set replication factor for each file.</li>
	<li>Data placement is much more flexible than what can be achieved with consistent hashing. A coordinator may choose to place a block on the local node to save network bandwidth or to place a block on the node that has low disk usage to balance the cluster.</li>
</ul>

<p>Using Cassandra to store metadata has also many advantages:</p>

<ul>
	<li>The Cassandra tabular data model is well suited for efficient storage and quick lookup of information about files and block locations. Metadata is tiny compared to data, and comprised of pieces of information of such types that Cassandra can handle well.</li>
	<li>Cassandra offers excellent scalability, with capacity not limited by the amount of memory available to a single server (such as for an HDFS NameNode). This means DSEFS can store a virtually unlimited number of files.</li>
	<li>The shared-nothing architecture of Cassandra offers strong high availability guarantees and allows DSEFS to be shared-nothing as well. Any node of your cluster may fail and DSEFS continues to work for both reads and writes. There are no special "master" nodes like HDFS NameNode. Hence, there are no single points of failure, even temporary. DSEFS clients can connect to any node of the DSE cluster that runs DSEFS.</li>
	<li>Cassandra lightweight transactions allow to make some operations atomic within a data center, e.g. if multiple clients in the same data center request to create the same path, at most one will succeed.</li>
	<li>Cassandra offers standard tools like&nbsp;cqlsh&nbsp;to query and manipulate data. In some cases it may be useful to have easy access to internal file system metadata structures, e.g. when debugging or recovering data.</li>
</ul>

<p>The following diagram shows how DSEFS nodes work together:</p>
<img alt="DSE Node" data-align="center" data-entity-type="file" data-entity-uuid="13e0db62-b5b6-4e60-ab37-d661f99885db" src="https://www.datastax.com/sites/default/files/inline-images/sq5djYIKEW9fAW_VaYgTSXQ.png" />
<p>Clients may talk to any node by HTTP to port 5598. The contacted node becomes the coordinator for the request. When accessing a file, the coordinator consults the metadata layer to check if the file exists, then to check permissions and finally to get the list of block identifiers and block locations. Then it fetches the blocks either from local block layer or from remote nodes by using DSEFS internode communication on port 5599. The coordinator joins blocks together and streams them to the client. In the future we may implement an optimization to skip the coordinator and request and join blocks directly by the client.</p>

<p>When writing a file, first the appropriate records are created in the metadata to register the new file, then the incoming data stream is split into blocks and sent to the appropriate block locations. After successfully writing a block, metadata is updated to reflect that fact.</p>

<h2>DSEFS Implementation</h2>

<p>DSEFS has been implemented in the Scala programming language. It uses&nbsp;<a href="https://netty.io/">Netty</a>&nbsp;for network connectivity, memory management and asynchronous task execution.</p>

<p>Netty together with&nbsp;<a href="https://github.com/scala/async">Scala-Async</a>&nbsp;allow for non-blocking, asynchronous style of concurrent programming, without callback hell and without explicit thread synchronization. A small number of threads is multiplexed between many connections. A request is always handled by a single thread. This thread-per-core parallelism model greatly improves cache efficiency, reduces the frequency of context switches and keeps the cost of connections low. Connections between the client and the server as well as between the nodes are persistent and shared by multiple requests.</p>

<p>DSEFS allocates buffers from off-heap memory with Netty pooled allocator. JVM heap is used almost exclusively for temporary, short-lived objects. Therefore DSEFS is GC friendly. When internally testing the DSEFS server in standalone mode, external to DSE, we've been able to use JVM heaps of size as low as 64 MB (yes, megabytes) without a noticeable drop in performance.</p>

<p>Contrary to CFS, DSEFS doesn't use the old Thrift API to connect to DSE. Instead, it uses&nbsp;<a href="https://github.com/datastax/java-driver">DataStax Java Driver</a>&nbsp;and CQL. CFS was the last DSE component using Thrift, so if you migrate your applications to DSEFS, you can simply disable Thrift API by setting cassandra.yaml&nbsp;start_rpc&nbsp;property to false.</p>

<h2>Conclusion</h2>

<p>DSE 5.1 comes with a modern, efficient, scalable and highly available distributed file system. There is no reason to use CFS any more. CFS has been deprecated but left available so you can copy your old data to the new file system.</p>

<p>For documentation on DSEFS visit:<br />
<a href="https://docs.datastax.com/en/dse/5.1/dse-dev/datastax_enterprise/analytics/dsefsTOC.html">https://docs.datastax.com/en/dse/5.1/dse-dev/datastax_enterprise/analytics/dsefsTOC.html</a></p>

<p>We'd love to get your feedback on your experience with DSEFS! Are there any features you want added?</p>


From CFS to DSEFS

Piotr Kołaczkowski

Share

More Technology

Getting Started with DataStax Astra DB and Amazon Bedrock

Why You Can't Miss Cassandra Summit

Mitigate the OpenAI Debacle with Open Source and Cloud

Supercharge AI Assistants with Superagent and DataStax

NoSQL and Vector DB
for Generative AI,
Instantly, At Scale

Piotr Kołaczkowski

Share

More Technology

Getting Started with DataStax Astra DB and Amazon Bedrock

Why You Can't Miss Cassandra Summit

Mitigate the OpenAI Debacle with Open Source and Cloud

Supercharge AI Assistants with Superagent and DataStax

NoSQL and Vector DBfor Generative AI,Instantly, At Scale

NoSQL and Vector DB
for Generative AI,
Instantly, At Scale