CloverDX 5.7 brings a job queue to better automatically manage load on the Server. The job queue protects the Server from CPU and memory overloading. Additionaly, new user's experience of Server is improved by a guided tour of the Server Console, with the help of a new Data Warehouse example. The installation and statup of the Server is more robust with the help of database update confirmation, better behavior in cluster and better progress reporting. The variant CTL type is integrated deeper into CloverDX.
The new job queue handles requests for job execution, and determines when to actually start each job. It manages the overall load on the Server to prevent CPU or memory overloading. This helps the Server especially in case of high production load and in cases of spikes of data processing.
In case of high CPU load or heap memory consumption, jobs are enqueued and wait to be started later. The job queue automatically starts the jobs later when the overall load decreases.
The Server Console monitoring and logging capabilities were extended to provide information about enqueued jobs. APIs and components were also extended. The job queue manages executions on each cluster node, and the cluster load balancer is aware of job queues of each node to better spread the load.
Use experience and learning curve of new users of Server is simplified by a new guided tour of the Server Console. The tour takes the users trough major parts of the Server and explains the main concepts.
To support the guided tour there is a new example. The Data Warehouse example shows a more complex scenario that uses a wider range of Server's functionality - jobs, schedules, listeners, data services etc.
We have improved the installation and upgrade process of Server to prevent some common issues and simplify the whole process.
User approval before changing database schema
Upgrades to a new Server version can require updates to the Server's database schema. We have modified this process to required user's approval in the Server Console. This helps to guide the users to create backups of the Server's database and to understand that this process might take some time.
For automation purposes, it is possible to disable this manual approval.
Parallel start of cluster nodes when upgrading
When upgrading CloverDX Cluster to a new version, it is now possible to start all nodes in parallel and only one of them will perform changes to the Server's database. So now it's not necessary to manually start the nodes in sequence to prevent database issues.
Reporting of progress during startup
The Server Console shows more detailed progress information during startup of the Server. You can see the where in the startup process the Server currently is, and you can see the Server's logs in the browser.
Facilitate SAML debugging
If single sign-on using SAML is enabled, it can be complex to analyze issues in the login process - communication problems, configuration issues etc. We've improved logging of SAML integration and we provide a way to enable more detailed logging.
The AWS and Azure Marketplace offerings with CloverDX Server were improved:
The CTL type "variant" was more integrated into the rest of the CloverDX stack:
To help you install or upgrade to this version, we've prepared a simple checklist:
Before You Upgrade
|Release||Compatibility/Upgrade notes, Features & Fixes||Published||Download|
|July 21, 2020||Documentation Download CloverDX 5.7 5.7.0|