DataStax Enterprise 3.2

Release Notes

DataStax Enterprise 3.2.x release notes cover these releases:

DataStax Enterprise 3.2.7 release notes

DataStax Enterprise 3.2.7 includes component changes, enhancements, resolved issues, and issues.

Components

The release updates Apache Cassandra to 1.2.18 and Apache Hadoop to 1.0.4.13.

Enhancements

  • This release provides a script for replacing the Snappy compression/decompressing library (snappy-java-1.0.5.jar) with snappy-java-1.0.4.1.jar. You need to replace the JAR on older RHEL-based Linux distributions, such as CentOS-5 only, and older Linux distributions to prevent the following error: GLIBCXX_3.4.9 not found. Run the script as follows on packaged installations:
    $ cd /usr/share/dse 
    $ switch-snappy 1.0.4

    On tarball installations, the script is in the bin directory.

  • The _HOST macro has been changed to force the hostname part of the Kerberos service principal to lowercase. The Kerberos service principal is generated from the host name, which can cause a problem connecting to cqlsh running if lowercase host names are not used.

Issues resolved

  • The problem causing the java.util.ConcurrentModificationException has been resolved by backporting a Cassandra fix (CASSANDRA-6841) to this release. (DSP-3162)
  • Hive no longer generates an error when a table does not have a column that is not a key. (DSP-3326)
  • Fixed the problem on Solr nodes that caused Tomcat to block shutdown when an out of memory error occurs. (DSP-3328)
  • Fixed the problem that alters MapReduce output returning multiple results, MAPREDUCE-1597, which causes large gzip files with a custom input format to be read multiple times. (DSP-3384)
  • Audit logging no longer throws a null pointer exception if a prepared statement uses a null value. (DSP-3447)
  • Fixed the out-of-memory error on huge clusters caused by Cassandra File System (CFS) memory consumption, which has been reduced significantly, approximately 500 times for some use cases. (DSP-3615)

Issues

  • DSE Search/Solr cannot index a document that indexes only one field, which is also the unique key in the schema and the primary key in the corresponding Cassandra table. DSE Search/Solr deletes any existing data with that primay key and does not return any results for such a query. (DSP-3362)

DataStax Enterprise 3.2.6 release notes

DataStax Enterprise 3.2.6 includes component changes, enhancements, resolved issues, and issues.

Components
  • Apache Cassandra 1.2.16.1 (updated)
  • Apache Hadoop 1.0.4.9
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.10 (updated)
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.12.2
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0
  • Apache Commons

Cassandra 1.2.16.1 supports CQL 3 and CQL2; CQL 2 is deprecated and removal is planned for Cassandra 3.0.

Enhancements and changes

DataStax Enterprise 3.2.6 includes the following enhancements and changes.
  • If vnodes are enabled on an Analytics or Solr node, an error is logged in the system log and an error appears in the output of the dsetool ring command.
  • Support for the Solr query join.
  • Support for the TimeUUIDTYPE Cassandra validator type. A value of the timeuuid type is a Type 1 UUID, which includes the time of its generation. Values are sorted, conflict-free timestamps. For example, use this type to identify a column, such as a blog entry, by its timestamp and allow multiple clients to write to the same partition key simultaneously.
  • If the cluster uses a Random or Murmur3 partitioner, the dsetool ring command warns you if the nodes are imbalanced. The dsetool compares nodes having the most and least load. If the ratio is greater than 1.1, a warning message appears.
Issues resolved
  • Fixed the problem causing a DSE 3.2 node to fail to start if you comment out or remove one of the following authentication/authorization sections but leave the other: (DSP-3078)
    • auth_replication_strategy: org.apache.cassandra.locator.SimpleStrategy
    • auth_replication_options: replication_factor: 1
  • A row of bad data is no longer inserted through CQL into fields using a copy directive. (DSP-3107)
  • Fixed an issue causing an Analytics node to throw an exception endlessly. (DSP-3130)
  • The dsetool rebuild_indexes command now returns an error code when it fails. (DSP-3178)
  • Fixed the issue that caused the DynamicSnitch to break the distributed search when load information changed during shard selection. (DSP-3322)
  • Fixed the issue preventing batch updates from being indexed if the updates were followed by a delete and were made on the same partition key. (DSP-3187)
  • Fixed an issue that caused the merging of Solr index segments to fail when using a custom sorting MergePolicy. (DSP-3230)
  • Using a composite unique key in a Solr schema with a Thrift-compatible table is no longer allowed. Attempting to load a schema under these conditions results in a message that the operation is not supported. (DSP-3232)
  • Fixed the issue that caused an assertion error when starting a Cassandra node with JVM_OPTS=-Dcassandra.join_ring=false. (DSP-3250)
  • Using the CQL native protocol, DataStax Enterprise now throws an appropriate exception when Kerberos authentication issues occur. (DSP-3293)
Issues
  • On older RHEL-based Linux distributions, such as CentOS-5 only, the following error might appear: GLIBCXX_3.4.9 not found. This error may also appear in older Linux distributions when installing DSE from the binary tarball. You must replace the Snappy compression/decompression library (snappy-java-1.0.5.jar) with snappy-java-1.0.4.1.jar. (DSP-3061)

DataStax Enterprise 3.2.5 release notes

DataStax Enterprise 3.2.5 release notes include component changes, enhancements, and resolved issues.

Components
  • Apache Cassandra 1.2.15.1 (updated)
  • Apache Hadoop 1.0.4.9
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.8 (updated)
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.12.2 (updated)
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0
  • Apache Commons

Cassandra 1.2.15.1 supports CQL 3 and CQL2; CQL 2 is deprecated and removal is planned for Cassandra 3.0.

Enhancements and changes

DataStax Enterprise 3.2.5 integrates updated Cassandra, Solr, and Sqoop components and adds the capability to change the HTTP interface to Apache JServe Protocol for use by DSE Search nodes.

Issues resolved

DataStax Enterprise 3.2.5 resolves the following issues:
  • Eased schema validation so that valid Solr field names in Cassandra can be created. (DSP-807)
  • Fixed the issue where the dse cassandra-stop command would not stop DSE plugins. (DSP-2837)
  • Fixed the issue where Solr would freeze when opening a corrupt index commit log. (DSP-2845)
  • Fixed the DSE Search issue with shaded spatial4j jar. (DSP-2880)
  • Fixed a race condition in Cassandra File System (CassandraFS) compaction that led Cassandra to attempt using already freed memory. (CASSANDRA-4934, DSP-2881)
  • Fixed the race condition that occurred during upgrading from Cassandra 1.1 to 1.2. (CASSANDRA-6619, DSP-2894)
  • Fixed the issue that caused a null pointer exception when upgrading SSTables using the upgradesstables utility on Cassandra indexes not backed by a table. (CASSANDRA-6645, DSP-2907)
  • Fixed the issue that caused client-node encryption (SSL) to fail on Solr nodes. (DSP-2947)
  • Fixed the issue causing only a single row to be expired from the Solr index when multiple rows share the same partition key. (DSP-2953)
  • Fixed the problem that prevented Hive from reading rows having null conditions. (DSP-2820, DSP-2956)
  • Fixed the cleanup that wasn't correctly removing old data from indexes backed by CQL3 tables. (DSP-2958)
  • Rows belonging to CQL3 tables having clustering columns were not correctly indexed during bootstrap of new nodes and execution of CQL3 batches, causing missed data in the index. This issue has been resolved. (DSP-2957)
  • Fixed the internal authentication issue when using cassandra-stress. (DSP-2911)

Issues

A DSE 3.2 node can fail to start if you comment out or remove one of the following sections but leave the other. (DSP-3078)

# Replication strategy to use for the auth keyspace.
     # Following an upgrade from DSE 3.0 to 3.1, this should be removed
     auth_replication_strategy: org.apache.cassandra.locator.SimpleStrategy

     # Replication options to use for the auth keyspace.
     # Following an upgrade from DSE 3.0 to 3.1, this should be removed
     auth_replication_options:
         replication_factor: 1

This can occur on either a fresh installation of 3.1-3.2 or on an upgrade from 3.0.

After the node is restarted the first time, the following error appears in system.log and when running nodetool ring:

ERROR 16:12:35,327 Exception in thread Thread[OptionalTasks:1,5,main] java.lang.RuntimeException
        at org.apache.cassandra.locator.AbstractReplicationStrategy.
        createReplicationStrategy(AbstractReplicationStrategy.java:274)
        at org.apache.cassandra.db.Table.createReplicationStrategy(Table.java:278)
Warning: To avoid this issue make sure that you comment out or remove both sections at once. If you restart the node a second time, it will fail to start, so do not restart any nodes once this error has occurred until you have performed one of the following workarounds. If you have already encountered the issue, use one of the following workarounds.

Workaround 1: The error is occurring but all nodes are still running

  1. Comment out both sections in the cassandra.yaml file:
    # Replication strategy to use for the auth keyspace.
    # Following an upgrade from DSE 3.0 to 3.1, this should be removed
    #auth_replication_strategy: org.apache.cassandra.locator.SimpleStrategy
    
    # Replication options to use for the auth keyspace.
    # Following an upgrade from DSE 3.0 to 3.1, this should be removed
    #auth_replication_options:
    #    replication_factor: 1
  2. Fix the replication strategy on the dse_auth keyspace using cqlsh:
    ALTER KEYSPACE dse_auth WITH replication = {
      'class': 'SimpleStrategy',
      'replication_factor': 1
    };
  3. Follow instructions for enabling internal security in the documentation.

Workaround 2: Some nodes are already down

  1. Perform steps 1-2 of the first workaround.
  2. On any nodes that do not start, move these directories from the system keyspace directory to a backup location:
    • Schema
    • Migrations
    • schema_columnfamilies
    • schema_columns
    • schema_keyspaces
  3. Restart the nodes. They should start and get the schema from the other nodes that are still running.
  4. Follow instructions for enabling internal security in the documentation.

Workaround 3: All of the nodes in the cluster are already down

  1. Perform steps 1-2 of the second workaraound.
  2. Start the nodes. The schema will now be empty.
  3. If you have a backup schema creation script written in cqlsh or cassandra-cli, replay the script to restore the schema after you start the nodes. If you do not have a backup, recreate the schema from memory to avoid losing the data.
  4. Follow instructions for enabling internal security in the documentation.

DataStax Enterprise 3.2.4 release notes

DataStax Enterprise 3.2.4 release notes include component changes, enhancements, and resolved issues.

Components

  • Apache Cassandra 1.2.13.2 (updated)
  • Apache Hadoop 1.0.4.9
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.7 (updated)
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.12.1
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0
  • Apache Commons

Enhancements

DataStax Enterprise 3.2.4 provides better capabilities for diagnosing a failure to initialize, caused by the misconfiguration of the bundled tomcat server.

Issues resolved

DataStax Enterprise 3.2.4 resolves these issues:

  • Fixed an issue that could cause very rare undefined behaviour when reading from CFS. (DSP-2732)
  • Changed the default value for back_pressure_threshold_per_core to 500 to balance indexing throughput and query responsiveness. (DSP-2732)
  • Fixed an issue that prevented shut down of nodes in a data center having two analytics nodes. (DSP-2770)
  • The fix for CASSANDRA-6510 has been backported to this release to resolve the problem related to dropping local mutations without a trace. (DSP-2812)
  • Sample cqlsh files that were not installed for packaged installations are now installed. (DSP-2828)

DataStax Enterprise 3.2.3 release notes

DataStax Enterprise 3.2.3 includes updated components and resolved issues.

Components

  • Apache Cassandra 1.2.13.1
  • Apache Hadoop 1.0.4.9
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.6
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.12.1
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0
  • Apache Commons

Apache documentation covers release notes for Cassandra 1.2.13 and earlier. Cassandra 1.2.13.1 supports CQL 3 and CQL2; CQL 2 is deprecated and removal is planned for Cassandra 3.0.

Issues resolved

  • Fixed the issue involving multiple dse cassandra -Dcassandra.replace_address commands. (DSP-2574)
  • Fixed the dsetool problem that caused failure if you used the short form arguments for jmxport and transport. (DSP-2743)
  • Fixed the DSE Search/Solr problem using non-string/non-numeric, such as date and boolean, CQL3 compound keys. For example, trying to delete rows having these keys caused an exception. (DSP-2798, DSP-2475)
  • Fixed a problem cause corruption in the saved cache file for the Cassandra File System. DataStax Enterprise now attempts to fix corrupted cfs files on startup and displays this warning in the logs: "Information about some removed CFS blocks has been lost, therefore physical removal of them by CFS compaction might be delayed." (DSP-2746)
  • Fixed Solr datatypes Datefield / TrieDateField storage of the millisecond portions of data when using the newer DSE-to-Solr type mapping version. (DSP-2801)
  • Fixed the issue that caused CQL Native connections to be refused when you enable internal authentication. (DSP-4097)

Issues

  • DSE Search supports the DirectSolrSpellChecker, but not the older Solr IndexBasedSpellChecker. Configure the DirectSolrSpellChecker for spell checking. (DSP-2756)

DataStax Enterprise 3.2.2 release notes

DataStax Enterprise 3.2.2 includes updated components, enhancements, and changes. These release notes also list issues and resolved issues.

Components

  • Apache Cassandra 1.2.12.2
  • Apache Hadoop 1.0.4.8
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.6
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.12.1
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0
  • Apache Commons

Apache documentation covers release notes for Cassandra 1.2.12 and earlier.

Enhancements and changes

This release includes an enhancement to the Solr Admin: a summary of information about the per-segment filter cache. In the Solr Admin, select a core, and then click Plugins / Stats. Expand dseFilterCache to see the information about the filter cache.

Issues resolved

This release resolves the following issues:

  • An same exception no longer appears in the log file when a node decommission, join, or update schema occurs. (DSP-1117)
  • Fixed the issue that caused problems when the Solr configuration set useColdSearcher to false. (DSP-1251)
  • Fixed the problem causing the Chrome browser to hang when this URL was used to request status: (DSP-2001)
    http://localhost:8983/solr/#/~cores?action=STATUS
  • Fixed the failure to elect a new job tracker after shutting down and starting up all nodes. (DSP-2627)
  • Health check exceptions no longer occur when running Solr workloads. (DSP-2631)
  • In the previous release, the packaged installation did not include two files, library-populate-cql.txt and library-cql.pig, which you can use to run the Explore Library Data example, a pig demo, manually. DataStax Enterprise 3.2.2 includes these files. (DSP-2655)
  • Fixed file handle leaks in the CassandraFS. (DSP-2660)
  • Fixed an issue with descending clustered order / reversed=true indexes not working with solr. (DSP-2690)
  • When upgrading to the latest DataStax Enterprise 3.2.x, a conflict occurs if you add new columns/fields to the Solr index. A change in the class name used to implement the Solr secondary index changed between versions. This issue has been resolved. (DSP-2697)
  • Fixed error when upgrading packages on Debian appears to corrupt the limits configuration. (DSP-2696)
  • Fixed a race condition when loading solr cores during an upgrade. (DSP-2702)
  • The issue that prevented one value from being written to a multi-valued field has been resolved. (DSP-2704)
  • Fixed the issue that caused a problem with the job tracker not starting properly after an upgrade. (DSP-2719)
  • Fixed an issue upgrading from 3.0.X to 3.2.X where Solr queries returned no results after the upgrade was complete. (DSP-2739)
  • Fixed an issue preventing Solr from using UUID primary keys. (DSP-2747)
  • Fixed an issue with auditing using batch mutations containing updates on counters. (DSP-2741)
  • Fixed an issue where Solr CQL3 reads pulled in all fields instead of the requested ones. Users should see a performance improvement. (DSP-2753)

Issues

This release has the following unresolved issues:

When upgrading to DataStax Enterprise 3.2.x from 3.0.x or earlier, schema disagreements are likely to occur. Issuing Solr queries might return incorrect results. When the output of DESCRIBE CLUSTER indicates a schema disagreement, or if a node is UNREACHABLE, perform these steps: (DSP-2751)

  1. Using the Command Line Interface (CLI), run the DESCRIBE CLUSTER command. For example:
    $ cassandra-cli -host localhost -port 9160
    
    [default@unknown] DESCRIBE cluster;

    If any node is UNREACHABLE, you see output something like this:

    [default@unknown] describe cluster;
    Cluster Information:
    Snitch: com.datastax.bdp.snitch.DseDelegateSnitch
    Partitioner: org.apache.cassandra.dht.RandomPartitioner
    Schema versions:
    UNREACHABLE: [10.202.205.203, 10.80.207.102, 10.116.138.23]
  2. Restart unreachable nodes.
  3. Repeat steps 1 and 2 until the DESCRIBE cluster command shows that all nodes have the same schema version number: only one schema version appears in the output of DESCRIBE cluster.

DataStax Enterprise 3.2.1 release notes

DataStax Enterprise 3.2.0 includes changes, resolved issues, and an upgrade issue.

Changes

  • DSE Search/Solr type checking is stronger in this release than in earlier releases. After upgrading, you might get error messages related to using an unsupported column type. Possible workarounds are:

    • Try changing the definition of a Cassandra table to use a supported type.

      If this does not work, error messages might say, for example, that the data is not in UTF-8 format.

    • Try re-importing the data as a supported type into the new database.

  • Added the following option in cassandra-env.sh:

    JVM_OPTS="$JVM_OPTS -Denable-old-dse-state=true

    After installing or upgrading the entire cluster, remove the above line on each node so it uses the new protocol, and perform a second rolling restart. See Version specific upgrade instructions and the install topics for your distribution.

    The cassandra-env.sh file is located in these directories:

    • Packaged installs: /etc/cassandra/
    • Tarball installs: install_location/conf/

Issues resolved

This release fixes the following issues:

  • Nodes return incomplete data after cold restarts. (DSP-2666)
  • Not found exceptions generated under heavy Solr indexing loads. (DSP-2629)

Issues

When upgrading to the latest DSE 3.2.x, a conflict occurs if you add new columns/fields to the Solr index. A change in the class name used to implement the Solr secondary index changed between versions. (DSP-2697)

This issue will be resolved in the next release. In the meantime, the workaround is to change the class name used in custom indexes to the old class name:

  • New class name

    com.datastax.bdp.search.solr.ThriftSolrSecondaryIndex

  • Old class name

    com.datastax.bdp.cassandra.index.solr.SolrSecondaryIndex

  1. For a tarball installation, after upgrading, restart a node in the cluster as a real-time Cassandra node instead of a Solr node. For a packaged installation, set SOLR_ENABLED=0 in the /etc/default/dse file.
  2. In cqlsh, use DESCRIBE SCHEMA to see the class names Cassandra attaches to your index definitions. The output would look something like this example:
    USE myks;
    CREATE TABLE survey (
     id int,
     age int,
     age_months int,
     age_unit text,
    . . .
    CREATE CUSTOM INDEX myks_survey_age_months_index ON survey (age_months) USING 'com.datastax.bdp.cassandra.index.solr.ThriftSolrSecondaryIndex';
    CREATE CUSTOM INDEX myks_survey_age_unit_index ON survey (age_unit) USING 'com.datastax.bdp.cassandra.index.solr.ThriftSolrSecondaryIndex';
    . . .
  3. In cqlsh, drop each index for your Solr data.
  4. Recreate each index, using exactly the same name, but add the USING clause shown in this example to specify the old class name.
    CREATE CUSTOM INDEX myks.age_months ON survey USING com.datastax.bdp.cassandra.index.solr.SolrSecondaryIndex;
  5. Restart the node as a Solr node.

DataStax Enterprise 3.2.0 release notes

DataStax Enterprise 3.2.0 includes updated components, enhancements, and changes. These release notes list issues and resolved issues.

Components

  • Apache Cassandra 1.2.11.2
  • Apache Hadoop 1.0.4.8
  • Apache Hive 0.9.0.4
  • Apache Pig 0.9.2
  • Apache Solr 4.3.0.2.4
  • Apache log4j 1.2.16
  • Apache Sqoop 1.4.2.3
  • Apache Mahout 0.6
  • Apache Tomcat 6.0.32
  • Apache Thrift 0.7.0

Apache documentation covers release notes for Cassandra 1.2.11 and earlier.

Enhancements and changes

  • General
    • Changes to the procedure for upgrading to DataStax Enterprise 3.2 have been made. Follow instructions in the upgrade documentation.
    • The agent for OpsCenter is included with the DataStax Enterprise install. It is called the DataStax Agent. You should always start the agent when launching DSE. See Starting DSE as a service and Staring DSE as a stand-alone process.
    • This release includes the yaml_diff tool that filters differences between two cassandra.yaml files, which is useful during upgrades. The new tool is located in the tools directory.
  • Solr
    • This release introduces Solr support for CQL 3, including tables having compound primary key columns and collections.
    • A new solrconfig.xml parameter queryExecutorThreads can be configured for multithreaded filter queries, normal queries, and doc values facets.
    • The DocSet creation for certain queries is now multithreaded.
    • Cassandra ring token fields in Lucene are warmed for faster queries on cold Lucene segments.
    • You can now import data into DSE Search/Solr from data sources, such as XML and RDBMS, using a configuration-driven Data Import Handler.
    • A new dse.yaml property, flush_max_time_per_core improves performance under heavy loads by setting a hard limit on the time to wait for asynchronous index updates. It is used in calculating dynamic backpressure settings, which help keep indexing queues relatively small, reduce GC pressure, and ensure that mutations are not dropped.
    • Solr core creation and reload now are processed in parallel instead of sequentially to save time. (DSP-2544)
    • You can now choose several strategies for shuffling the shards to suit your load-balancing needs. (DSP-2544)
    • Solr commits now occur in parallel (DSP-2394)
    • The shard selection algorithm has been improved to rank the nodes for selection that are not performing Solr indexing higher than indexing ones. If only indexing nodes can satisfy the query, the query will not fail but instead return potentially partial results. (DSP-2066)
    • DSE Search now uses the direct bytebuffer for the off-heap DSENRTCachingDirectory instead of the RAMDirectory used by the NRTCachingDirectory, which creates numerous byte[] objects on heap. (DSP-1248)
  • Hadoop

Issues

  • Older RHEL-based Linux distributions, such as CentOS-5 only.
    GLIBCXX_3.4.9 not found. 

    This error may appear in older Linux distributions when installing DSE from the binary tarball. You must replace the Snappy compression/decompression library (snappy-java-1.0.5.jar) with snappy-java-1.0.4.1.jar. (DSP-2189)

  • In CQL 3-backed cores, Solr schema fields that are dynamic and multivalued are not supported.
  • Non-string/non-numeric types, such as dates, booleans, as a Solr key are not supported.
  • When upgrading to the latest DSE 3.2.x, a conflict occurs if you add new columns/fields to the Solr index. A change in the class name used to implement the Solr secondary index changed between versions. This issue will be resolved in DataStax Enterprise 3.2.2. In the meantime, perform the workaround for this release. (DSP-2697)

Issues resolved

  • Fixed error where setting max_solr_concurrency_per_core parameter to 1 caused error. (DSP-2321)
  • Clarified startup output by changing the message from "Waiting for nodes to become alive . . ." to "Wait for nodes completed. . ." (DSP-2350)
  • Fixed issue where JT would change from node to node under constant pressure. (DSP-2418)
  • The problem randomly manifested with the exception in the summary has been fixed. (DSP-2519)
  • Fixed issue of Job Tracker moving from one node to another. (DSP-2520)
  • Fixed the problem that returned incorrect values when applications set widerows=true or set the cassandra.range.batch.size=1. (DSP-2537)
  • Fixed the problem that caused secondary indexes to work unreliably with row caches. (DSP-2551)
  • Include and set up the old snappy for older distributions. (DSP-2567)
  • Fixed the issue involving long-running repairs on Solr admin keyspace that prevented timely core create/reload operations on large clusters. (DSP-2570)
  • Fixed the issue involving multiple dse cassandra -Dcassandra.replace_address commands. (DSP-2574)
  • Fixed potential stack overflow during range tombstones insertion (CASSANDRA-6181)
  • Limited CQL prepared statement cache by size instead of count (CASSANDRA-6107)
  • Fixed indexed queries with row cache enabled on parent table (CASSANDRA-5732)
  • Skipped replaying mutations that pass CRC but fail to deserialize (CASSANDRA-6183)
  • Fixed memory leak in snapshot repair (CASSANDRA-6047)
  • Updated default LCS SSTable size to 160MB (CASSANDRA-5727)
Show/hide