5.0.1
New features
- 4 new Best Practice rules:
- Oracle JRE is being used
- JNA is properly enabled
- At least 2 seeds specified per data center
- Use different interfaces for
listen_address
and
rpc_address
when possible
- Improved dashboard loading
- Added date/time controls to zoomed graphs
- Support for provisioning all recommended EC2 sizes
- Always display data center name on the Ring tab, even if there is only one data
center
- Larger Alerts window for more comfortable viewing
Resolved issues
- Fixed issue with UI not recognizing any clusters (displaying the Welcome screen) when the browser does not have an internet connection (OPSC-3285)
- Fixed positioning of nodes on the Ring view in multi-data center and mixed vnode environments
(OPSC-3256)
- Fixed memory leaks related to frequent and/or large Data Backup jobs (OPSC-2219)
- Fixed issues with Dashboard preset migrations when upgrading to 5.0.x (OPSC-3373)
- Fixed memory leak in Nodes section of the UI (OPSC-3345)
- Properly display
AVAILABLE
for the Performance Service when using
DataStax Enterprise 4.5 or greater. (OPSC-3245)
- Properly retrieve streaming status based on the version of Cassandra in your cluster
(OPSC-3335)
- Fixed issue with inability to display metrics for some Solr cores (OPSC-3220)
- Fixed restoring schemas and data with certain non-ASCII characters (OPSC-3184)
- Fixed overwriting
num_tokens
when configuring a node that doesn't have
num_tokens
set (OPSC-3003)
- Many more minor fixes