DataStax Distribution of Apache Cassandra release notes

DataStax Distribution of Apache Cassandra release notes cover cluster requirements, upgrade guidance, security updates, changes and enhancements, issues, and resolved issues.

DataStax Distribution of Apache Cassandra™ (DDAC) release notes cover cluster requirements, upgrade guidance, components, changes and enhancements, issues, and resolved issues .
Note: Each point release includes a highlights and executive summary section to provide guidance and add visibility to important improvements.

Requirement for Uniform Licensing

All nodes in each DataStax licensed cluster must be uniformly licensed to use the same subscription. For example, if a cluster contains 5 nodes, all 5 nodes within that cluster must be either DataStax Distribution of Apache Cassandra™, or all 5 nodes must be DataStax Enterprise. Mixing different subscriptions within a cluster is not permitted. The DataStax Advanced Workloads Pack may be added to any DataStax Enterprise (not DataStax Distribution of Apache Cassandra) cluster in an incremental fashion. For example, a 10-node DSE cluster may be extended to include 3 nodes of the Advanced Workloads Pack. “Cluster” means a collection of nodes running the software which communicate with one another using gossip. See Enterprise Terms.

Note: For third-party software, see DataStax Enterprise 5.1.x third-party software (not all entries apply to DDAC).

Before you upgrade

Upgrade advice Compatibility
Before you upgrade to a later major version, upgrade to the latest patch release (5.1.19) on your current version. Be sure to read the relevant upgrade documentation. DDAC supports patch upgrades starting with DDAC patch 5.1.11.
Check the compatibility page for your products. DDAC does not support DSE OpsCenter or DataStax Studio.
See Upgrading DataStax drivers. DataStax Drivers: You may need to recompile your client application code.
Use DataStax Bulk Loader for loading and unloading data. Loads data into DDAC and unloads data from any Apache Cassandra™ 2.1 or later data source.

DataStax recommends upgrading to the latest patch release (5.1.19). Be sure to read the relevant upgrade documentation.

DDAC Compatibility

DDAC patch 5.1.18

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.18.

jvm.options

The location of the jvm.options file depends on the type of installation:

Package installations
Installer-Services installations

 /etc/dse/cassandra/jvm.options

Tarball installations
Installer-No Services installations

 installation_location/resources/cassandra/conf/jvm.options
Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.18.
Important: DataStax recommends the latest patch release for most environments.

29 April 2020

DDAC patch 5.1.18 is compatible with Apache Cassandra™ 3.11 and adds production-certified changes to Cassandra.

5.1.18 DDAC patch core

Changes and enhancements:

  • Dropping and re-adding the same column with incompatible types is not supported. This change prevents unreadable SSTables. (DB-3586)
  • Added anticompaction to nodetool stop command help menu. (DB-3821)
  • Improved error messaging for enabled internode SSL encryption in Cassandra Tools test suite. (DB-3957)
  • Security updates:

Resolved issues:

  • Error retrieving expired columns with secondary index on key components. (DB-3764)
  • Using SELECT JSON for empty BLOB values incorrectly returns an empty string instead of the expected 0x. (DSP-20022)
  • Error retrieving expired columns with secondary index on key components. (DB-3764)
  • Read inconsistencies. (CASSANDRA-12126) (DB-3873)

Enhancements for DDAC patch 5.1.18

A list of DataStax Distribution of Apache Cassandra patch 5.1.18 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.18 includes this production-certified change and all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)
  • Validate value sizes in LegacyLayout. (CASSANDRA-15373)
  • Handle paging states serialized with a different version than the session's. (CASSANDRA-15176)
  • Toughen up column drop and recreate type validations. (CASSANDRA-15204)
  • Use bounds instead of range for SSTables in anti-compaction. (CASSANDRA-14411)

General upgrade advice for DDAC patch 5.1.18

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.18.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.17

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.17.

Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.17.
Important: DataStax recommends the latest patch release for most environments.

2 October 2019

DDAC patch 5.1.17 is compatible with Apache Cassandra™ 3.11 and adds production-certified changes to Cassandra.

5.1.17 database core highlights

  • Standalone cqlsh client tool provides an interface for developers to interact with the database and issue CQL commands without having to install the database software. From DataStax Labs, download the version of CQLSH that corresponds to your DataStax database version. (DSP-18694)

5.1.17 DDAC patch core

Changes and enhancements:
  • Improved troubleshooting. A log entry is now created when autocompaction is disabled or enabled for a table. (DB-1635)
  • Reformatted StatusLogger output to reduce details in the INFO level system.log. The detailed output is still present in the debug.log. (DB-2552)
  • Prevent changing the replication strategy of system keyspaces. (DB-2960)
  • New nodetool commands to get current values: getcachecapacity, getcachekeystosave, and gethintedhandoffthrottlekb. (DB-3618)
  • Update Jackson Databind to 2.9.9.1 for all components except DataStax Bulk Loader. (DSP-19441)
Resolved issues:
  • Fix to prevent NPE during repair in mixed-version clusters. (DB-1985)
  • Tarball installs to create two instances on the same physical server with remote JMX access with binding the separated IPs to port 7199 causes JMX error of Address already in use (Bind failed) because com.sun.management.jmxremote.host is ignored. (DB-2483)
  • sstablepartitions incorrectly handles -k and -x options. (DB-3442)

    Workaround: To specify multiple keys, repeat the -k or -x option several times.

  • After upgrades from DSE 4.8 to DSE 5.0 or DSE 5.1, deleted data might be resurrected when rows were deleted on DSE 4.8 tables with multiple collection columns. (DB-3492)

    This fix provides protection from this potential condition. Reappearing rows are naturally fixed by compaction.

    Note: If you experience reappearing data after upgrading from DSE 4.8, DataStax recommends running nodetool scrub to correct potentially affected SSTables.
  • Reads against older version ma and mc SSTables hit more SSTables than necessary due to the bug fixed by CASSANDRA-14861. (DB-3691)
    Attention: DataStax recommends reading and following all upgrade instructions in Upgrading DDAC documentation. Do not skip the upgrade step to upgrade the SSTables on each node to ensure that all SSTables are on the current version. If the SSTables are already on the current version, the command returns immediately and no action is taken. See DataStax Enterprise, Apache Cassandra, CQL, and SSTable compatibility.
  • Upgraded Apache MINA Core library to 2.0.21 to prevent a security issue where Apache MINA Core was vulnerable to information disclosure. (DSP-19213)
  • Error in custom provider prevents DSE node startup. With this fix, the node will start up but insights is not active. See the DataStax Support Knowledge Base for steps to resolve existing missing or incorrect keyspace replication problems. (DSP-19521)
  • Latency metrics, like dse_client_request_latency_bucket, are not present. (DSP-19549)
Known issues:
  • On Oracle Linux 7.x, StorageService.java:4970 exception occurs with DSE package installation. (DSP-19625)

    Workaround: On Oracle Linux 7.x operating systems, install DSE using the binary tarball.

Enhancements for DDAC patch 5.1.17

A list of DataStax Distribution of Apache Cassandra patch 5.1.17 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.17 includes this production-certified change and all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)

  • Skipping illegal legacy cells can break reverse iteration of indexed partitions. (CASSANDRA-15178)
  • Skip cells with illegal column names when reading legacy SSTables. (CASSANDRA-15086)
  • SSTable min/max metadata can cause data loss. (CASSANDRA-14861)

General upgrade advice for DDAC patch 5.1.17

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.17.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.16

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.16.

Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.16.
Important: DataStax recommends the latest patch release for most environments.

9 July 2019

DDAC patch 5.1.16 is compatible with Apache Cassandra™ 3.11 and includes all DataStax enhancements from earlier versions.

5.1.16 DDAC patch

Enhancements for DDAC patch 5.1.16

A list of DataStax Distribution of Apache Cassandra patch 5.1.16 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.16 includes all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)

General upgrade advice for DDAC patch 5.1.16

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.16.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.15

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.15.

Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.15.
Important: DataStax recommends the latest patch release for most environments.

11 June 2019

DDAC patch 5.1.15 is compatible with Apache Cassandra™ 3.11 and adds production-certified changes to Cassandra.

5.1.15 DDAC patch

Resolved issues:

  • Improved logging identifies which client, keyspace, table, and partition key is rejected when mutation exceeds size threshold. (DB-1051)
  • Nodes in a cluster continue trying to connect to a decommissioned node. (DB-2886)
  • Bootstrap should fail if the node is not able to fetch the schema from other nodes in the cluster. (DB-3186)
  • Slow startup or node hangs when encryption is used. (DB-3050)

Enhancements for DDAC patch 5.1.15

A list of DataStax Distribution of Apache Cassandra patch 5.1.15 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.15 includes this production-certified change and all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)

General upgrade advice for DDAC patch 5.1.15

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.15.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.14

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.14.

Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.14.
Important: DataStax recommends the latest patch release for most environments.

16 April 2019

DDAC patch 5.1.14 is compatible with Apache Cassandra™ 3.11 and adds production-certified changes to Cassandra.

5.1.14 DDAC patch highlights

  • Fixed anti-compaction transaction for atomicity and index building. (DB-3016)
  • Remedy deadlock during node startup when calculating disk boundaries. (DB-3028)

5.1.14 DDAC patch

Resolved issues:

  • Native server Message.Dispatcher.Flusher task stalls under heavy load. (DB-1814)
  • Reference leak in SSTableRewriter in sstableupgrade when keepOriginals is true. (DB-2944)
  • Anti-compaction transaction causes temporary data loss. (DB-3016)
  • Check of two versions of metadata for a column fails on upgrade from DSE 5.0.x when type is not of same class. Loosen the check from CASSANDRA-13776 to prevent Trying to compare 2 different types ERROR on upgrades. (DB-3021)
  • Deadlock during node startup when calculating disk boundaries. (DB-3028)
  • Correct handling of dropped UDT columns in SSTables. (DB-3031)
  • Mishandling of frozen in complex nested types. (DB-3081)
  • cqlsh EXECUTE AS command does not work. (DB-3098)
  • Security: java-xmlbuilder is vulnerable to XML external entities (XXE). (DSP-13962)
  • Timestamp PK routing on solr_query fails. (DSP-18223)
  • Leak in BulkTableWriter. (DSP-18513)

Enhancements for DDAC patch 5.1.14

A list of DataStax Distribution of Apache Cassandra 5.1.14 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.14 includes this production-certified change and all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)

  • Severe concurrency issues in STCS,DTCS,TWCS,TMD.Topology,TypeParser (CASSANDRA-14781)

General upgrade advice for DDAC patch 5.1.14

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.14.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.13

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.13.

Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.13.
Important: DataStax recommends the latest patch release for most environments.

27 February 2019

DDAC patch 5.1.13 includes all changes from previous versions and is compatible with Apache Cassandra™ 3.11 and includes all production-certified changes from previous releases.

Enhancements for DDAC patch 5.1.13

A list of DataStax Distribution of Apache Cassandra patch 5.1.13 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.13 includes all enhancements from previous DDAC patch releases. (For updates, see CHANGES.txt.)

General upgrade advice for DDAC patch 5.1.13

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.13.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.12

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.12.

cassandra.yaml

  • The cassandra.yaml file is located in the installation_location/conf directory.
Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.12.
Important: DataStax recommends the latest patch release for most environments.

26 December 2018

DDAC patch 5.1.12 is compatible with Apache Cassandra™ 3.11 and includes production-certified changes to Cassandra.

5.1.12 DDAC patch highlights

  • Skip fetching streamed range in repair during consistent-replace. (DB-2596)
  • Fixed user-defined aggregates (UDAs) that instantiate user-defined types (UDTs) break after restart. (DB-2771)
  • Fixed NullPointerException that can occur during compaction if users use TWCS and allow_unsafe_aggressive_sstable_expiration. (DB-2472)
  • Fixed resource leak related to streaming operations that affects tiered storage users. Excessive number of TieredRowWriter threads causing java.lang.OutOfMemoryError. (DB-2463)
  • General stability improvements:
    • Invalidate chunk cache on SSTable rename. (DB-2594)
    • Fixes to several thread-safety bugs. (DB-2602, DB-2609)
    • Fix for static and regular collision when using same ColumnIdentifier and ComposedTypes. (DB-1630)
  • Upgrade improvements:
    • Fixed handling of deletions for dropped collections in static rows in mixed-version clusters. (DB-2341)
  • Operational improvements:
    • Support for QUORUM/LOCAL_QUORUM consistent replace_address. (DB-1577, DB-2596)
    • Expose information about stored hints by using JMX/nodetool listendpointspendinghints. (DB-1674)
    • New sstablepartitions tool to identify large partitions. (DB-803)
    • Fixed incorrect order of application of nodetool garbagecollect leaves tombstones that should be deleted. (DB-2658)
    • Custom HeapDumpPath is not overwritten. (DB-714)
    • By default, rebuild only locally replicated keyspaces. (DB-2301)

5.1.12 DDAC patch

Changes and enhancements:

  • New DDAC start-up parameter -Ddse.consistent_replace improves LOCAL_QUORUM and QUORUM consistency on new node after node replacement. (DB-1577)
  • New nodetool listendpointspendinghints command prints hint information about the endpoints this node has hints for. (DB-1674)
  • New sstablepartitions tool to identify large partitions. (DB-803)

Resolved issues:

  • Custom HeapDumpPath is overwritten. (DB-714)
  • Deleting a static column and adding it back as a non-static column introduces corruption. (DB-1630)
  • Rebuild should not fail when a keyspace is not replicated to other datacenters. (DB-2301)
  • Corrupted static collection deletions for dropped collections in mixed-version clusters. (DB-2341)
  • repair may skip some ranges due to received range cache. (DB-2432)
  • Excessive number of TieredRowWriter threads causing java.lang.OutOfMemoryError (DB-2463)
  • NullPointerException during compaction on table with TimeWindowCompactionStrategy (TWCS). (DB-2472)
  • Prevent potential SSTable corruption with nodetool refresh. (DB-2594)
  • The nodetool gcstats command output incorrectly reports the GC reclaimed metric in bytes, instead of the expected MB. (DB-2598)
  • TypeParser is not thread safe. (DB-2602)
  • STCS, DTCS, TWCS, TMD aren't thread-safe. (DB-2609)
  • Incorrect order of application of nodetool garbagecollect leaves tombstones that should be deleted. (DB-2658)
  • User-defined aggregates (UDAs) that instantiate user-defined types (UDTs) break after restart. (DB-2771)

Enhancements for DDAC patch 5.1.12

A list of DataStax Distribution of Apache Cassandra patch 5.1.12 enhancements to Apache Cassandra™ 3.11.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.12 includes all changes from previous DDAC patch releases. These production-certified changes are enhancements to Apache Cassandra™ 3.11. (For updates, see CHANGES.txt.)

  • Legacy sstables with multi block range tombstones create invalid bound sequences (CASSANDRA-14823)
  • Expand range tombstone validation checks to multiple interim request stages (CASSANDRA-14824)
  • Reverse order reads can return incomplete results (CASSANDRA-14803)
  • Avoid calling iter.next() in a loop when notifying indexers about range tombstones (CASSANDRA-14794)
  • Fix purging semi-expired RT boundaries in reversed iterators (CASSANDRA-14672)
  • DESC order reads can fail to return the last Unfiltered in the partition (CASSANDRA-14766)
  • Fix corrupted collection deletions for dropped columns in 3.0 <-> 2.{1,2} messages (CASSANDRA-14568)
  • Handle failures in parallelAllSSTableOperation (cleanup/upgradesstables/etc) (CASSANDRA-14657)
  • Improve TokenMetaData cache populating performance avoid long locking (CASSANDRA-14660)
  • Fix static column order for SELECT * wildcard queries (CASSANDRA-14638)
  • sstableloader should use discovered broadcast address to connect intra-cluster (CASSANDRA-14522)
  • Fix reading columns with non-UTF names from schema (CASSANDRA-14468)
  • Fix incorrect cqlsh results when selecting same columns multiple times (CASSANDRA-13262)
  • Returns null instead of NaN or Infinity in JSON strings (CASSANDRA-14377)

General upgrade advice for DDAC patch 5.1.12

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.12.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.

DDAC patch 5.1.12

Operations

  • A new property cassandra.range_tombstone_bound_check_chance checks for bad range tombstone on a percentage of queries. The default is 0.01 (can be set in range of 0.0 - 1.0).

DDAC patch 5.1.11

Release notes for DataStax Distribution of Apache Cassandra patch 5.1.11.

cassandra-env.sh

  • The cassandra-env.sh file is located in the installation_location/conf directory.
Release notes for DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.11.
Important: DataStax recommends the latest patch release for most environments.

14 September 2018

DDAC is compatible with Apache Cassandra™ 3.11.0 and adds production-certified changes and enhancements.

5.1.11 DDAC patch

Changes and enhancements:

  • Connections on non-serialization errors are not dropped. (DB-2233)
  • Create a log message when DDL statements are executed. (DB-2383)

Resolved issues:

  • Set MX4J_ADDRESS to 127.0.0.1 if not explicitly set. (DB-1950)
  • Digest mismatch for same data between nodes with flushed memtables and nodes with non-flushed memtables. (DB-1980)
  • Fix handling of start bound in legacy paged queries. (DB-1984)
  • Move TWCS message "No compaction necessary for bucket size" to Trace level or NoSpam. (DB-2022)
  • Limit max cached direct buffer on NIO to 1 MB. (DB-2028)
  • Compaction strategy instantiation errors don't generate meaningful error messages, instead return only InvocationTargetException. (DB-2404)
  • Non-portable syntax (MX4J bash-isms) in cassandra-env.sh broke service scripts. (DB-2123)
  • nodetool upgradesstables fails with 20-year TTL. After upgrade to 5.1.11, take required action. (DB-2109)
  • Add missing equality sign to SASI schema snapshot. (DB-2129)
  • For tables using DSE Tiered Storage, nodetool cleanup places cleaned SSTables in the wrong tier. (DB-2173)
  • sstableloader options assume the RPC/native (client) interface is the same as the internode (node-to-node) interface. (DB-2184)
  • Audit events for CREATE ROLE and ALTER ROLE with incorrect spacing exposes PASSWORD in plain text. (DB-2285)
  • Client warnings are not always propagated via LocalSessionWrapper. (DB-2304)
  • Timestamps inserted with ISO 8601 format are saved with wrong millisecond value. (DB-2312)
  • Compaction fails with IllegalArgumentException: null. (DB-2329)
  • BulkLoader class exits without printing the stack trace for throwable error. (DB-2377)

Enhancements for DDAC patch 5.1.11

A list of DataStax Distribution of Apache Cassandra patch 5.1.11 enhancements to Apache Cassandra™ 3.1.10.

DataStax Distribution of Apache Cassandra™ (DDAC) patch 5.1.11 includes all changes from previous releases. These production-certified changes are enhancements to Apache Cassandra™ 3.11.0. (For updates, see CHANGES.txt.)

  • Fix static column order for SELECT * wildcard queries (CASSANDRA-14638)
  • sstableloader should use discovered broadcast address to connect intra-cluster (CASSANDRA-14522)
  • Fix reading columns with non-UTF names from schema (CASSANDRA-14468)
  • Validate supported column type with SASI analyzer (CASSANDRA-13669)
  • Remove BTree.Builder Recycler to reduce memory usage (CASSANDRA-13929)
  • Reduce nodetool GC thread count (CASSANDRA-14475)
  • Fix New SASI view creation during Index Redistribution (CASSANDRA-14055)
  • Remove string formatting lines from BufferPool hot path (CASSANDRA-14416)
  • Update metrics to 3.1.5 (CASSANDRA-12924)
  • Detect OpenJDK jvm type and architecture (CASSANDRA-12793)
  • Don't use guava collections in the non-system keyspace jmx attributes (CASSANDRA-12271)
  • Fix corrupted static collection deletions in 3.0 -> 2.{1,2} messages (CASSANDRA-14568)
  • Fix potential IndexOutOfBoundsException with counters (CASSANDRA-14167)
  • Always close RT markers returned by ReadCommand#executeLocally() (CASSANDRA-14515)
  • Reverse order queries with range tombstones can cause data loss (CASSANDRA-14513)
  • Fix regression of lagging commitlog flush log message (CASSANDRA-14451)
  • Add Missing dependencies in pom-all (CASSANDRA-14422)
  • Cleanup StartupClusterConnectivityChecker and PING Verb (CASSANDRA-14447)
  • Fix deprecated repair error notifications from 3.x clusters to legacy JMX clients (CASSANDRA-13121)
  • Cassandra not starting when using enhanced startup scripts in windows (CASSANDRA-14418)
  • Fix progress stats and units in compactionstats (CASSANDRA-12244)
  • Better handle missing partition columns in system_schema.columns (CASSANDRA-14379)
  • Delay hints store excise by write timeout to avoid race with decommission (CASSANDRA-13740)
  • Incorrect counting of pending messages in OutboundTcpConnection (CASSANDRA-11551)
  • Fix compaction failure caused by reading un-flushed data (CASSANDRA-12743)

General upgrade advice for DDAC patch 5.1.11

General upgrade advice for DataStax Distribution of Apache Cassandra patch 5.1.11.

All upgrade advice from previous versions applies. Carefully review the Upgrading DDAC planning and upgrade instructions to ensure a smooth upgrade and avoid pitfalls and frustrations. This general advice applies to the database upgrade and does not replace the upgrade documentation.
  • General upgrading advice for any version and new features for Apache Cassandra are in NEWS.txt. Be sure to read the NEWS.txt all the way back to your current version.
  • See also the Apache Cassandra changes in CHANGES.txt.