<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aaron Ploetz on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/aaron-ploetz/</link><description>Articles written by Aaron Ploetz on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Jun 2022 20:36:25 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/aaron-ploetz/index.xml" rel="self" type="application/rss+xml"/><item><title>Tombstones and Ghost Data Don’t Have to Be Scary!</title><link>https://foojayio.github.io/website/today/tombstones-and-ghost-data-dont-have-to-be-scary/</link><pubDate>Thu, 09 Jun 2022 20:36:25 +0000</pubDate><guid>https://foojayio.github.io/website/today/tombstones-and-ghost-data-dont-have-to-be-scary/</guid><description>&lt;p&gt;&lt;img src="https://foojayio.github.io/website/today/tombstones-and-ghost-data-dont-have-to-be-scary/1_g5MhVmTyqdCWG_-LkItmNg-1024x679.jpeg" alt="" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Working with tombstones can be one of the more frustrating aspects of Apache Cassandra®. Problems with tombstones can happen when a large number of deletes occur within a short period of time, resulting in slower queries and disk bloat. This article will discuss tombstones, including the purpose they serve, and strategies/methods on how to avoid them.&lt;/strong&gt;&lt;/em&gt;{#2508}&lt;/p&gt;
&lt;p&gt;&lt;a href="https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/index.html#why-tombstones" target="_blank" rel="noopener noreferrer"&gt;Tombstones&lt;/a&gt;
 in &lt;a href="https://cassandra.apache.org/_/index.html" target="_blank" rel="noopener noreferrer"&gt;Apache Cassandra&lt;/a&gt;
&lt;em&gt;®&lt;/em&gt; are written markers that are created whenever a value is deleted. Their purpose is to indicate that any prior values have been deleted. When a read occurs, it pulls data from the sorted string table (SSTable) files on a node that may contain the data. All prior values for the requested key are returned, ordered by write-time.{#d711}&lt;/p&gt;</description></item></channel></rss>