- FAQ - Can DSEFS be used without running DSE nodes in Analytics mode?
- Node fails to start with "Error: Could not find or load main class com.datastax.bdp.DseModule"
- High CPU usage on one node in DSE 6
- How to manually collect logs in DataStax Enterprise for Support
- Compaction and memtable flush failing with null AssertionError from IncrementalTrieWriterPageAware.java
- "Schema version mismatch detected" on restarting a node
- Nodes report "Unexpected protocol magic number!" error in logs
- Lightweight transactions failing, conditional writes not getting processed
- FAQ - Why Java performance utilities like jps no longer work in DSE 5.0+
- FAQ - Why is forcing major compaction on a table not ideal?
- DSE Advanced Replication reports error while fetching mutations "Could only read 0 but expected 1 bytes"
- DSE Advanced Replication returns UnsupportedMutationException for collection columns
- AssertionError thrown by Materialized View update of a null base row
- SELECT with a filter on timestamp column does not return data
- DSE won't start because cannot bind to port 8609
- JVM OOM direct buffer errors affected by unlimited java.nio cache
- Number of replicas required does not match the CL being used
- Hints file with unknown CFID can cause nodes to fail
- FAQ - How to split large SSTables on another server
- Bulkload data between TDE enabled clusters
- OpsCenter STOMP connection issues on nodes with separate network interfaces
- FAQ - How to attach large files to a Support ticket
- DSE5.1.0 node will not start if vnodes split across disks
- Table read failures after dropping a column post-upgrade to DSE 5.x
- DSE 5.0 cqlsh cannot connect to earlier versions of Cassandra, results in "ProtocolError"
- High server load and latency when CPU frequency scaling is enabled
- High number of connections can exhaust available native threads for Cassandra JVM
- nodetool repair always shows the total number of ranges in the entire cluster
- Manual Backup and Restore, with Point-in-time and table-level restore.
- Nodes showing DN in nodetool status with "invalid gossip generation" warning in logs
