- DSE 5.0 SSTables with UDTs corrupted after upgrading to DSE 5.1, 6.0, or 6.7
- FAQ - What does "FailureDetector - Not marking nodes down due to local pause" mean?
- DSE fails to start with `java.nio.charset.MalformedInputException`
- HOW TO - Mirror DSE packages internally
- HOW TO - Check if DSE TieredCompactionStrategy is in use
- HOW TO - Correlate high LWT usage to an application
- HOW TO - Check the DSE version running on a node
- HOW TO - Attach or upload files to a support ticket
- Compaction fails with CorruptSSTableException, AssertionError recycling a memory buffer
- Nodes become unresponsive during high app traffic periods when mmap is enabled on DSE 6
- sstableloader fails with "UnrecoverableKeyException: Password verification failed"
- Errors configuring DSBulk 1.3 with SSL enabled
- Increased memory use on nodes after upgrading to DSE 5.0 or DSE 5.1
- HOW TO - Specify composite partition keys for SSTable utilities
- FAQ - What does SSTable compression ratio in tablestats indicate?
- DSE startup fails with "Failed to dispatch hints file", "file is corrupted"
- When authentication is enabled, completed jobs information cannot be viewed using Spark Worker UI
- Repair streams fail with "AssertionError: UnfilteredPartitionIterator should not contain empty partitions"
- NodeSync service startup returns AssertionError with message "No tables will be validated by NodeSync."
- FAQ - Use of disk_access_mode in DSE 5.1 and earlier
- Memory only strategy will throw mlock error if disk_access_mode set incorrectly
- 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"
- dsetool throws NullPointer exception (NPE) when commands are executed
- 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
- Message seen in logs "Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB"
- Nodes report "Unexpected protocol magic number!" error in logs
