DataStax Enterprise Analytic nodes are powered by Apache Hadoop running on top of Apache Cassandra. Both Hadoop and Cassandra come with their own sets of library dependencies. Additionally, Hadoop relies on running user-code, which may often want to load its own set of dependencies. As long as each module uses a distinct set of dependencies, there are no problems. However, when two modules running within the same JVM need to use different versions of the same library, a library conflict arises. In this blog post I shortly describe how DSE internally manages library dependencies, and our current approach to resolving library conflicts. I'll also uncover some little bits of internal DSE classloader architecture.
We are in the process of completely redesigning the OpsCenter user interface.
DataStax OpsCenter has always allowed users to run common operations such as cleanup and repair on individual nodes.
A major iceberg that sits waiting to crash into many data-driven online applications is running out of capacity.
Repairing a Cassandra cluster resolves inconsistencies amongst replicas for a given range of data.