Welome to the DataStax Support Blog. Here you will find articles that cover the entire range of topics related to using DataStax Products, tips on best practices while using DataStax products, as well as insights on how to make your experience with Support as efficient and pleasant as possible.

Be sure to check out our hours of free training and downloads on DataStax Academy . For industry topics and general DataStax news, head over to our company blog or check out the DataStax developer blog for deep dives into a wide range of subject matter.

March 22, 2018 • By: Thanh Tran

There is a big improvement in DSE v5.1.6 that makes it much easier to debug LDAP authentication issues compared to earlier versions of DSE.  Here, we will look at using the DSE v5.1.6 improvement to debug LDAP authentication.  We will also talk about LDAP authentication debugging methods to use with older versions of DSE.

February 07, 2018 • By: Ben Krug

In Cassandra, data isn’t deleted in the same way it is in RDBMSs. Cassandra is designed for high write throughput, and avoids reads-before-writes. It uses sstables, which are immutable once written. So, a delete is actually an update, and updates are actually inserts (into new sstables). A “tombstone” marker is written to indicate that the data is now (logically) deleted. 

February 05, 2018 • By: Gregory Smith

Since DSE 4.8, DataStax Enterprise has leveraged logback for all logging. Logback has many advantages over the older log4j logging project, one of the main benefits is the ability to change the logging configuration dynamically, without the need to restart the DSE software. This is particularly useful in a production environment where obtaining permission to restart production nodes may not be possible.

January 24, 2018 • By: Devin Suiter

Don't end up on HN as a horror story about data loss and unusable restore options! Devin Suiter shines a little light on the ins and outs of backup options in DSE.

January 16, 2018 • By: Dan Yuen

With the help of work by Elisabeth Kübler-Ross, this is what you might expect when your DataStax Architect, Lead DBA or other key contributor resigns.