Altinity.Cloud Release Notes

Most recent releases organized by major release and release date:

Altinity.Cloud 23.2.33

The Backup configuration is now available on a cluster level
- Different clusters can now have different backup settings
New volume performance guidelines when starting a cluster
Users are now alerted that profile setting is used instead of a server setting
New resource limit for total number of nodes
Can now exclude an individual node from a load balancer
Users can now add custom Grafana dashboards
Support for using alternate cluster names
Changes for Altinity staff only:
- Added New Altinity Support role
- Discounts management

The SHARE button has been renamed to INVITE
The Rescale screen now shows storage units
“Kafka Connection Check” has been moved to the Cluster page
Notifications now include FQDN for cluster names
Environment dashboard improvements
Changes to environment backup settings are now automatically applied to clusters
Additional DataDog regions now available

Fixed “Copy Data between Clusters” for Anywhere environments with custom node taints
Fixed a bug in Node View where they were not available for offline nodes
Rebalance is back and available for envadmins

Clone database feature that allows to clone database w/o data copy on same host
Force restart of an individual node
Show pod events in a node view
Current quota usage is now displayed on an environment screen
User role can be specified when inviting user to an environment
Progress bar when applying changes to a cluster
Operator managed persistence is now default for new environments, and can be turned on for existing ones. It allows to re-scale volumes w/o downtime
Re-publish ZK clusters

Backup configuration is currently always deployed, even if schedule is disabled
ClickHouse version recommendations were improved
IAM-managed access to backup bucket is now allowed
Data rebalance UI has been improved
Cluster are now sorted alphabetically
Asynchronous metrics log frequency is reduced for new clusters
Changed some ‘default’ profile settings (part of operator release):
- Enabled ‘do_not_merge_across_partitions_select_final’
- Set ’load_balancing’ to ’nearest_hostname’
- Set niceness (‘os_thread_priority’) to 2.

Fixed a bug with version upgrades for ClickHouse 23.1 and above that might result in cluster not going online after restart
Fixed a bug with “Workload->Replication” screen did not display any results
Fixed a bug with “Copy Data Between Clusters” tool that did not work correctly in a replicated cluster with non-partitioned tables in some cases
Display an error message if “Schema Consistency -> Create table on all nodes” fails with an error

User is notified with a warning sign when backups are not configured
User is notified with a popup message when data migration is completed or failed
‘Delete table’ action is added to Data Consistency tab
List of databases granted to ClickHouse user are displayed
Quick filter was added in order to see unhealthy nodes on a Dashboard page
Cluster tags for GCP environments in order to split costs by clusters

‘Environment Settings’ was renamed to ‘Environment Variables’ on the cluster page
DBA tools UI was made more intuitive
Improved new Anywhere environment setup process
Improved ‘Data Rebalance’ function that could sometimes move too much data
Backup configuration is moved to a separate resource instead of being bundled with ClickHouse configuration. This change requires restart.
Backup stability improvements, upgrade clickhouse-backup to 2.1.3 version
Upgraded clickhouse-operator to 0.20.1
n2d-standard-64 is now available by default for GCP clusters

Fixed a bug when node status was not updated for a few minutes after ClickHouse cluster is up an running
Fixed a bug with backup being restored from AWS to GCP environments or vice versa could fail due to mismatching node types
Fixed a bug when Rescale ignored auto publishing being turned off
Fixed a bug when ‘Run DDL ON CLUSTER’ did switch off automatically when specific node is selected
Fixed a bug with rescaling GCP clusters in old tenants
Fixed a bug when profile settings could not be changed on a cluster that can not start
Fixed Data Migration tool that did not work in Anywhere environments due to hard-coded tolerations
Fixed a bug with backup compression format was not respected for GCP clusters
Fixed a bug with memory and volume graphs displaying incorrect data

The GitHub repository for this project is located at: