Skip to content

6.4.0 Yellowbrick Release Notes

Date: Aug 29, 2023

Yellowbrick Version 6.4.0 Release Notes

Yellowbrick Data Warehouse Version 6.4.0 is supported for AWS and Microsoft Azure cloud deployments. This version of Yellowbrick Data Warehouse is installed on Cloud Data Warehouse Manager (CDWM) Version 3.64.x.

Cloud ProviderCDWM VersionYellowbrick Data Warehouse VersionKubernetes Version
AWS3.64.x6.4.0EKS 1.23
Azure3.64.x6.4.0AKS 1.25

Upgrade and Compatibility Requirements

Read the following information before beginning an upgrade to Version 6.4.0. Contact Customer Support to review the process and schedule the upgrade.

Upgrades from Version 6.3.x to 6.4.0 are supported. These upgrades apply to both CDWM and data warehouse instances.

Note: Before attempting to upgrade data warehouse instances, make sure they are running. You cannot upgrade suspended instances.

AWS Upgrades from Version 6.3.x

Version 6.4.0 requires EKS Version 1.23. You must use the EKS migration tool to upgrade to Version 1.23 before upgrading to Version 6.4.0.

For each Yellowbrick upgrade:

  1. Upgrade CDWM in Yellowbrick Manager.
  2. Upgrade your data warehouse instances in Yellowbrick Manager. Before upgrading data warehouse instances, make sure they are running. You cannot upgrade suspended instances.

Azure Upgrades from Version 6.3.x

You have to upgrade from 6.3.x to 6.4.0, upgrade from prior versions are not allowed.

You can upgrade directly from Version 6.3.x to Version 6.4.0. Note that Version 6.4.0 requires AKS Version 1.25, but this version is supplied as part of the Yellowbrick upgrade.

To update AKS from 1.24 to 1.25 (CDWM 3.63 to 3.64 and Yellowbrick 6.3 to 6.4), start by upgrading data warehouse instances. Do not upgrade CDWM first. Follow these steps:

  1. Upgrade your Version 6.3 data warehouse instances to Version 6.4.0. Before upgrading data warehouse instances, make sure they are running, and that they have a running default cluster. You cannot upgrade suspended instances.

  2. Suspend all of your data warehouse instances, regardless of whether they have been upgraded.

  3. Create the upgrade template by using the following azure-cli command:

az ts create \
          --name <template-spec-name> \
          --version 1.25 \
          --resource-group <resource-group-name> \
          --subscription <subscription-name> \
          --location <location> \
          --template-file install/azureresourcemanager/output/build/containers/installer-scripts/yb-cdw-aks-upgrade.json \
          --ui-form-definition install/azureresourcemanager/output/build/containers/installer-scripts/upgradeFormDefinition.json

Note

<template-spec-name>, <resource-group-name>, <subscription-name>, and <location> will need to be replaced with your own information.

  1. In the Microsoft Azure Portal, search for the newly created template spec under Template specs. Select the template spec and click Deploy. On the Basics panel, verify the subscription, resource group, and Kubernetes version are accurate, input the desired Kubernetes cluster, and then select Create. The process may take up to 30 minutes to complete. When the deployment is complete, the AKS and CDWM versions should both have been upgraded.

  2. Verify the Kubernetes version in the Azure Portal by searching for Kubernetes services, selecting the Kubernetes cluster name entered in the previous step, and checking under Overview. Verify the CDWM version by going to the Yellowbrick Manager, selecting Configuration, and looking under Warehouse Manager.

Upgrades from Version 5.x (Not Supported)

You cannot upgrade from Version 5.x to Version 6.4.0. However, you can replicate databases from some older releases to Version 6.4.0; see BAR2 and Replication Compatibility.

ybtools Compatibility

Yellowbrick recommends that you always upgrade ybtools to match the Yellowbrick server version you are running (for example, upgrade to ybtools Version 6.4 before connecting to a Version 6.4 database). In most cases, using an older version of ybtools, such as 5.2 or 6.3, to connect to a Version 6.3 database will work but is not recommended.

Using Version 6.4 of ybtools with an older server version (such as Version 6.3 or 5.2) may result in error messages for some commands or a mismatch between client and server features.

The Version 5.2 and 5.4 ybtools packages install two sets of backup and restore tools: legacy tools (BAR1) and current versions of the tools (BAR2). The legacy tools are deprecated and have been removed from the 6.x releases.

BAR2 and Replication Compatibility

Important: The source and target systems used for database backup and restore (BAR2) and database replication must be compatible. To support full functionality, the source and target systems should both be running a 6.3 version of Yellowbrick software.

Nonetheless, you can back up and restore a database, or replicate a database, from:

  • 5.2.x to 6.4.x
  • 5.4.3 or later to 6.4.x
  • 6.1.x to 6.4.x
  • 6.2.x to 6.4.x
  • 6.3.x to 6.4.x
  • 6.4.x to 6.4.x

Although you can start replication from a 5.2, 5.4, 6.1, or 6.2, or 6.3 source to a 6.4 target, and you can fail over to the 6.4 target, you cannot fail back to the 5.2, 5.4, 6.1, 6.2, or 6.3 source. In general, you cannot fail back to a Yellowbrick version with a catalog version that is earlier than the current catalog version.

Known Issues in Version 6.4.0

You may encounter the following issues in Version 6.4.0. Contact Customer Support for additional information.

| Release | Issue | Description | | 6.4.0 | 32571, 32542 | The Java-based client tools (ybload, ybunload, ybbackup, ybrestore) do not support the --auth-token connection option. Support for this option will be added in a future release. |

Fixed Issues in Version 6.4.0

The following issues are fixed in Version 6.4.0.

ReleaseIssueDescription
6.4.031836During AWS deployment, the Kubernetes external-dns software attempts to create DNS records in the most-specific variant when multiple Route 53 zones are present in a hierarchy. The documentation now states that you must either specify values for the most-specific variant, or values for a different DNS zone that does not have overlaps.
6.4.029683In Version 6.4.0, the database row store alert message has been improved to indicate that it is the catalog row store that is becoming full.

Parent topic:Change History