diff --git a/docs/content/preview/architecture/docdb-replication/async-replication.md b/docs/content/preview/architecture/docdb-replication/async-replication.md index dbeb3197126b..53322f2675d6 100644 --- a/docs/content/preview/architecture/docdb-replication/async-replication.md +++ b/docs/content/preview/architecture/docdb-replication/async-replication.md @@ -161,12 +161,11 @@ Today, this is done by backing up the source universe and restoring it to the ta Ongoing work, [#17862](https://github.com/yugabyte/yugabyte-db/issues/17862), will replace using backup and restore here with directly copying RocksDB files between the source and target universes. This will be more performant and flexible and remove the need for external storage like S3 to set up replication. - ## Supported deployment scenarios xCluster currently supports active-active single-master and active-active multi-master deployments. -### Active- active single-master +### Active-active single-master Here the replication is unidirectional from a source universe to a target universe. The target universe is typically located in data centers or regions that are different from the source universe. The source universe can serve both reads and writes. The target universe can only serve reads. Since only the nodes in one universe can take writes this mode is referred to as single master. Note that within the source universe all nodes can serve writes. diff --git a/docs/content/preview/releases/yba-releases/v2024.1.md b/docs/content/preview/releases/yba-releases/v2024.1.md index 9cc8da06d704..7c16c2af89da 100644 --- a/docs/content/preview/releases/yba-releases/v2024.1.md +++ b/docs/content/preview/releases/yba-releases/v2024.1.md @@ -27,6 +27,171 @@ If you have a Replicated installation, you must migrate from Replicated to YBA I YugabyteDB 2024.1.0.0 and newer releases do not support v7 Linux versions (CentOS7, Red Hat Enterprise Linux 7, Oracle Enterprise Linux 7.x), Amazon Linux 2, and Ubuntu 18. If you're currently using one of these Linux versions, upgrade to a supported OS version before installing YugabyteDB v2024.1.0. Refer to [Operating system support](/stable/reference/configuration/operating-systems/) for the complete list of supported operating systems. {{}} +## v2024.1.1.0 - July 31, 2024 {#v2024.1.1.0} + +**Build:** `2024.1.1.0-b137` + +**Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2024.1.1.0/yugabytedb-2024.1.1.0-b137-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2024.1.1.0/yugabytedb-anywhere-2024.1.1.0-b137-third-party-licenses.html) + +### Download + + + +### Highlights + +**CDC Observability** {{}} + +YugabyteDB Anywhere supports monitoring the status of replication slots when using [PostgreSQL Logical Replication Protocol](/stable/explore/change-data-capture/using-logical-replication/) for Change Data Capture (CDC). + +For more information, refer to [CDC Observability](/stable/yugabyte-platform/alerts-monitoring/cdc-observability/). + +### New features + +* [Provider validation](/stable/yugabyte-platform/configure-yugabyte-platform/aws/#create-a-provider). When creating public cloud providers (for AWS, Azure, GCP) and Kubernetes providers, YugabyteDB Anywhere now performs validation checks on some user-inputted fields, reducing downstream errors and speeding the configuration process. +* [Support for Exporting Metrics to a Separate, External Prometheus](/stable/yugabyte-platform/alerts-monitoring/prometheus-custom/). YugabyteDB Anywhere supports export of universe time-series metrics to an external Prometheus instance. The documentation shows how to do this for both VM-based and Kubernetes-based universes. + +
+ View the detailed changelog + +### Improvements + +* Changes the default permission to `600` for the backup manifest file to accommodate immutable NAS devices. PLAT-13578 +* Adds a toggle in the UI to suppress health check notifications during maintenance windows. PLAT-13856 +* Allows Ansible tasks to run seamlessly even with very long host names by using hash for Ansible/SSH control path. PLAT-13938 +* Allows setting up of YugabyteDB in AWS Singapore Government's GCC Plus environment by extending AZ name limit from 25 to 100 characters. PLAT-13212 +* Introduces a new feature, `tablet guardrail mechanism`, that triggers a warning when the ratio of live tablet peers to the supportable tablet peers is more than 0.9, and a severe alert when it's more than 1.0. Available from 2024.1 onwards. PLAT-13520 +* Turns off "assign public IP" option in Azure create universe by default. PLAT-13948 + +### Bug fixes + +* Enables usage of underscores in GCS bucket names during GCP Backup configuration. PLAT-13266 +* Enables consistent generation of new incremental backup times in the event of clock skewness. PLAT-13375 +* Allows users to filter out resolved alert notifications via WebHook channel configuration. PLAT-13506 +* Stops health check alerts during an active maintenance window by introducing a new parameter, `SuppressHealthCheckNotificationsConfig`, to the `MaintenanceWindow` model class and its APIs. PLAT-13518 +* Allows deletion of expired, aborted, or failed backups, removes redundant backups when a schedule is deleted, retries backup deletion before marking it as `Failed To Delete`, and queues ongoing deletions for later when YBA restarts. PLAT-13750 +* Lets users rotate node-to-node certificates alone without client-to-node encryption enabled. PLAT-13806 +* Unsnoozes all universe level health check notifications to encourage use of the maintenance window function. PLAT-13928 +* Corrects the checksum mismatch in the V342 migration to ensure successful upgrades from 2.14 to later branches. PLAT-13977 +* Automatically re-fetches access tokens before expiring for continuous user sessions when `offline_access` scope is set. PLAT-14042,PLAT-11246 +* Allows runtime configuration get API to return the correct inherited value, not just the parent scope value. PLAT-14090 +* Conceals DB user's password to prevent exposure in the application log during the upgrade procedure. PLAT-14286 +* Adjusts yml task to retain the last old release during the release GC process. PLAT-14368 +* Corrects the calculation of affected nodes in the certificate alerts message. PLAT-14385 +* Reduces security risks by storing hashed API tokens instead of actual tokens in the users table. PLAT-8028 +* Allows backing up, avoiding repetitive full backup tasks and updating incremental backup time only after passing all validation checks. PLAT-14497 +* Fixes the issue of tests failing at create universe on Itests Alma8 AMI due to expired GPG keys. PLAT-14136 +* Eliminates file descriptor leaks enhancing database stability. PLAT-13665 +* Removes the misuse of defaultImageBundle in universe when custom AMI is specified using YBA's machineImage. PLAT-13800 +* Allows for updated machineImage passing from nodeDetails in disk operations, preventing edit universe tasks failure due to missing AMIs in AWS clusters. PLAT-13808 +* Upgrades PostgreSQL version to the latest 42.3.x addressing critical vulnerabilities. PLAT-13824 +* Redirects stderr logs in yb_backup.py to prevent kubectl warn logs from disrupting remote command executions. PLAT-14012 +* Allows error-free query for releases with artifacts of a specific deployment type by excluding artifacts without a linked release. PLAT-14057 +* Ensures Edit Kubernetes Universe tasks only re-run after validating previous task parameters. PLAT-14203 +* Allows the collect_metrics.timer and bind_check.service to operate independently, avoiding system hang-ups due to cyclic dependency issues. PLAT-14293 +* Corrects the failure of Azure Provider validation due to unexpected mandatory fields. PLAT-14530 +* Repairs build failure in CentOS 7 pex/yugabundle builder Docker image. PLAT-14543 +* Corrects the failure of Azure Provider validation due to unexpected mandatory fields. PLAT-14530 +* Fixes software upgrade process to ensure master nodes are correctly categorized as `inactive` or `active`. PLAT-14561,PLAT-14153 +* Adjusts missing backport in version 2024.1.1 to correct discrepancy in default core file component value label from bytes to GB. PLAT-14593 +* Upgrades go etcd and cyphar dependencies in yba-installer, enhancing security by fixing vulnerabilities. PLAT-12335 +* Upgrades mina-core package to a secure version 2.2.3 and paramiko to a non-vulnerable version 3.4.0. PLAT-12336 +* Eliminates duplicate `exported_instance` label from Prometheus targets of DB exported metrics. PLAT-12808 +* Changes `localProvider` key from `task` to `input` for its availability during sbt tasks. PLAT-13367 +* Updates AWS metadata to include new regions. PLAT-13623 +* Removes internal flags related to providers now enabled by default. PLAT-13743 +* Lets you store node metrics in the yb_home directory instead of the /tmp directory. PLAT-13755 +* Hides autoflags from the display when listing gflags in the user interface. PLAT-13794 +* Upgrades python cryptography to 42.0.4 and setuptools to 65.5.1, enhancing security. PLAT-13836,PLAT-13835 +* Ensures CPU architecture selection is enabled for all providers, not just AWS, improving DB Versions API usage. PLAT-13852 +* Alters snooze alert behavior to also suppress universe health check alerts during maintenance windows. PLAT-13857 +* Fixes an issue that caused data from newer backups to be wrongly restored during the restoration of older backups. PLAT-13905 +* Allows normal workflows like systemd upgrade to function even when AMI is deleted from the cloud console. PLAT-13971 +* Resolves the issue of universe creation failure due to incorrect Image Bundle UUID by using the specified ec2-user. PLAT-14004 +* Nullifies possibility of Null Pointer Exception when using old storage config based proxy without username. PLAT-14143 +* Allows default use of M-series instance types on AWS. PLAT-14196 +* Prevents removal of overrides during volume resizing in Kubernetes. PLAT-14198 +* Changes permissions to allow traverse through `yb_home` directory, facilitating the collection of custom metrics. PLAT-14216 +* Ensures keyspace is not left empty during restore API requests, preventing restoration issues. PLAT-14221 +* Adds ConnectOnly role to LDAP group table constraint for better access control. PLAT-14230 +* Enables setting of sshUser/Port from the overrides for backward compatibility, fixing Provider Edit to successfully update image Bundle. PLAT-14244 +* Allows handling of large output in remote commands to prevent hanging. PLAT-14342 +* Fixes the `current lag` stat in xCluster to be table & stream specific, not influenced by other universes. PLAT-14425 +* Enhances yba installer migrations to skip certain versions during backporting which can be applied later on upgrades. PLAT-14511 +* Fixes issue where clicking preview clears data and doesn't display correct information when setting up ysql_ident or ysql_hba multiline flags. PLAT-14515 +* Allows customization of the yba installer timeout duration to avoid process failure due to long startups. PLAT-14443 +* Allows processing of all local releases during an import without failing due to local file issues. PLAT-14532 +* Allows fetching of static flags metadata for version 2.16+ from DB package when editing gflags via UI. PLAT-14533 +* Allows YBA to call `need_bootstrap` for older universes without the `indexed_table_id`, preventing errors. PLAT-14540 +* Removes SystemdUpgrade from IN_TRANSIT list to address failures on -gcp-rf3 on master build. PLAT-13770 +* Refines empty list component styling and deactivates the action button on linux version catalog when no versions are present for consistency. PLAT-13776,PLAT-13807 +* Allows increasing tserver volume size in edit universe mode for K8 and enables resize of master volumes. PLAT-13920 +* Allows display of total CPU usage graph in YBA metrics pages alongside user and system CPU usage. PLAT-14025 +* Introduces `follower_lag_ms` metric to the dashboard for easier identification of lagging masters and struggling tservers. PLAT-14254 +* Adds validation to disallow the non-restart upgrade option during rollback. PLAT-14390 +* Eliminates deprecated `vnetName/securityGroupId` fields from the region object during provider editing. PLAT-14802 +* Reduces local Provider's flakiness by using dedicated temporary directories and separate nfs backup directory. PLAT-13252 +* Allows safe extraction of DB files in a multi-thread environment by synchronizing conflicting buffer reads. PLAT-14160 +* Resolves an issue in yb_backup.py where the `stderr` keyword argument was incorrectly passed. PLAT-14208 +* Facilitates handling multiple comma-separated hostnames in YBA installer, enhancing template files, status commands, and reconfiguration wait times. PLAT-13096 +* Increases YBC client and server version to 2.1.0.1-b1, optimizing catalog version mechanism. PLAT-14575 +* Adjusts missing backport in version 2024.1.1 to correct discrepancy in default core file component value label from bytes to GB. PLAT-14593 +* Fixes user interface issues concerning the releases UX design, ensuring consistency across various modal and panel displays. PLAT-14607 +* Updates the log file names for YB-Controller logs and adds missing symlink `yb-controller-server.{INFO|WARN|ERROR}` to enhance troubleshooting. PLAT-14609,PLAT-14594 +* Allows preserving the uploaded YBDB builds by relocating the directory, solving the issue of directory deletion after container restarts. PLAT-14655 +* Upgrades go etcd and cyphar dependencies in yba-installer, enhancing security by fixing vulnerabilities. PLAT-12335 +* Upgrades mina-core package to a secure version 2.2.3 and paramiko to a non-vulnerable version 3.4.0. PLAT-12336 +* Eliminates duplicate `exported_instance` label from Prometheus targets of DB exported metrics. PLAT-12808 +* Changes `localProvider` key from `task` to `input` for its availability during sbt tasks. PLAT-13367 +* Updates AWS metadata to include new regions. PLAT-13623 +* Removes internal flags related to providers now enabled by default. PLAT-13743 +* Lets you store node metrics in the yb_home directory instead of the /tmp directory. PLAT-13755 +* Hides autoflags from the display when listing gflags in the user interface. PLAT-13794 +* Upgrades python cryptography to 42.0.4 and setuptools to 65.5.1, enhancing security. PLAT-13836,PLAT-13835 +* Ensures CPU architecture selection is enabled for all providers, not just AWS, improving DB Versions API usage. PLAT-13852 +* Alters snooze alert behavior to also suppress universe health check alerts during maintenance windows. PLAT-13857 +* Fixes an issue that caused data from newer backups to be wrongly restored during the restoration of older backups. PLAT-13905 +* Allows normal workflows like systemd upgrade to function even when AMI is deleted from the cloud console. PLAT-13971 +* Resolves the issue of universe creation failure due to incorrect Image Bundle UUID by using the specified ec2-user. PLAT-14004 +* Nullifies possibility of Null Pointer Exception when using old storage config based proxy without username. PLAT-14143 +* Allows default use of M-series instance types on AWS. PLAT-14196 +* Prevents removal of overrides during volume resizing in Kubernetes. PLAT-14198 +* Changes permissions to allow traverse through `yb_home` directory, facilitating the collection of custom metrics. PLAT-14216 +* Ensures keyspace is not left empty during restore API requests, preventing restoration issues. PLAT-14221 +* Adds ConnectOnly role to LDAP group table constraint for better access control. PLAT-14230 +* Enables setting of sshUser/Port from the overrides for backward compatibility, fixing Provider Edit to successfully update image Bundle. PLAT-14244 +* Allows handling of large output in remote commands to prevent hanging. PLAT-14342 +* Fixes the `current lag` stat in xCluster to be table & stream specific, not influenced by other universes. PLAT-14425 +* Enhances yba installer migrations to skip certain versions during backporting which can be applied later on upgrades. PLAT-14511 +* Fixes issue where clicking preview clears data and doesn't display correct information when setting up ysql_ident or ysql_hba multiline flags. PLAT-14515 +* Allows customization of the yba installer timeout duration to avoid process failure due to long startups. PLAT-14443 +* Allows processing of all local releases during an import without failing due to local file issues. PLAT-14532 +* Allows fetching of static flags metadata for version 2.16+ from DB package when editing gflags via UI. PLAT-14533 +* Allows YBA to call `need_bootstrap` for older universes without the `indexed_table_id`, preventing errors. PLAT-14540 +* Upgrades YBC client and server version to 2.1.0.1-b3 for better compatibility with both Alma 8.9 and centOS 7 universes. PLAT-14722 +* Removes SystemdUpgrade from IN_TRANSIT list to address failures on -gcp-rf3 on master build. PLAT-13770 +* Refines empty list component styling and deactivates the action button on linux version catalog when no versions are present for consistency. PLAT-13776,PLAT-13807 +* Allows increasing tserver volume size in edit universe mode for K8 and enables resize of master volumes. PLAT-13920 +* Allows display of total CPU usage graph in YBA metrics pages alongside user and system CPU usage. PLAT-14025 +* Introduces `follower_lag_ms` metric to the dashboard for easier identification of lagging masters and struggling tservers. PLAT-14254 +* Adds validation to disallow the non-restart upgrade option during rollback. PLAT-14390 +* Eliminates deprecated `vnetName/securityGroupId` fields from the region object during provider editing. PLAT-14802 +* Updates task_uuid as a key label for proper in-memory updates, enhancing task analysis capabilities. PLAT-14017 +* Reduces local Provider's flakiness by using dedicated temporary directories and separate nfs backup directory. PLAT-13252 +* Allows safe extraction of DB files in a multi-thread environment by synchronizing conflicting buffer reads. PLAT-14160 +* Resolves an issue in yb_backup.py where the `stderr` keyword argument was incorrectly passed. PLAT-14208 +* Facilitates handling multiple comma-separated hostnames in YBA installer, enhancing template files, status commands, and reconfiguration wait times. PLAT-13096 +* Increases YBC client and server version to 2.1.0.1-b1, optimizing catalog version mechanism. PLAT-14575 +* Ensures nodes no longer get stuck in "VM image upgrade" state after upgrading the Linux version. PLAT-14731 + +
+ ## v2024.1.0.0 - June 4, 2024 {#v2024.1.0.0} **Build:** `2024.1.0.0-b129` diff --git a/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16-anywhere.md b/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16-anywhere.md index 0a4d0510f888..d21b03a17568 100644 --- a/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16-anywhere.md +++ b/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16-anywhere.md @@ -34,10 +34,6 @@ type: docs ## Release notes -{{< tip title="YugabyteDB Anywhere release notes have moved" >}} -The release notes for YugabyteDB Anywhere have moved here. The [YugabyteDB v2.16 release notes](../../ybdb-releases/v2.16/) (and all other releases) are still available in their original location. -{{< /tip >}} - Included here are the release notes for all releases in the **YugabyteDB Anywhere** (YBA) v2.16 series. Content will be added as new notable features and changes are available in the patch releases of the YBA v2.16 series. For an RSS feed of all release series to track the latest product updates, point your feed reader to the [RSS feed for releases](../../index.xml). @@ -54,7 +50,7 @@ If you're using a previous v2.16 database version, you won't be able to successf **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.8.0/yugabytedb-2.16.9.0-b67-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.9.0/yugabytedb-anywhere-2.16.9.0-b67-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features @@ -82,7 +78,7 @@ For instructions on downloading and installing YugabyteDB Anywhere, refer to [In **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.8.0/yugabytedb-2.16.8.0-b16-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.8.0/yugabytedb-anywhere-2.16.8.0-b16-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Improvements @@ -187,7 +183,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.7.0/yugabytedb-2.16.7.0-b59-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.7.0/yugabytedb-anywhere-2.16.7.0-b59-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Improvements @@ -241,7 +237,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.6.1/yugabytedb-2.16.6.1-b1-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.6.1/yugabytedb-anywhere-2.16.6.1-b1-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Bug fixes @@ -253,7 +249,7 @@ For instructions on downloading and installing YugabyteDB Anywhere, refer to [In **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.6.0/yugabytedb-2.16.6.0-b43-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.6.0/yugabytedb-anywhere-2.16.6.0-b43-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features @@ -312,7 +308,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.5.0/yugabytedb-2.16.5.0-b24-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.5.0/yugabytedb-anywhere-2.16.5.0-b24-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Improvements @@ -347,7 +343,7 @@ N/A -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features @@ -393,7 +389,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.3.0/yugabytedb-2.16.3.0-b43-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.3.0/yugabytedb-anywhere-2.16.3.0-b43-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features @@ -440,7 +436,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.2.0/yugabytedb-2.16.2.0-b41-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.2.0/yugabytedb-anywhere-2.16.2.0-b41-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Improvements @@ -498,7 +494,7 @@ This is a database-only release, with no changes to YugabyteDB Anywhere. **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.1.0/yugabytedb-2.16.1.0-b50-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.1.0/yugabytedb-anywhere-2.16.1.0-b50-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features @@ -564,7 +560,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.0.1/yugabytedb-2.16.0.1-b7-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.0.1/yugabytedb-anywhere-2.16.0.1-b7-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### Improvements @@ -587,7 +583,7 @@ N/A **Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2.16.0.0/yugabytedb-2.16.0.0-b90-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2.16.0.0/yugabytedb-anywhere-2.16.0.0-b90-third-party-licenses.html) -For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../yugabyte-platform/install-yugabyte-platform/). +For instructions on downloading and installing YugabyteDB Anywhere, refer to [Install YugabyteDB Anywhere](../../../../yugabyte-platform/install-yugabyte-platform/). ### New features diff --git a/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16.md b/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16.md index 10457223e098..d3f20b36f99c 100644 --- a/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16.md +++ b/docs/content/preview/releases/ybdb-releases/end-of-life/v2.16.md @@ -34,14 +34,8 @@ type: docs ## Release notes -{{< tip title="YugabyteDB Anywhere release notes have moved" >}} -The [release notes for YugabyteDB Anywhere](../../yba-releases/) have moved to [their own page](../../yba-releases/v2.16/). -{{< /tip >}} - What follows are the release notes for the YugabyteDB v2.16 series. Content will be added as new notable features and changes are available in the patch releases of the YugabyteDB v2.16 series. -For an RSS feed of all release series to track the latest product updates, point your feed reader to the [RSS feed for releases](../index.xml). - {{< warning title="Technical Advisory: Use database version 2.16.1.1 or later" >}} YugabyteDB releases in the v2.16 series prior to v2.16.1.1 contain a backup issue: if a database contains a pre-split range-partitioned table whose _primary key constraint column ordering_ isn't the same as the _table's column ordering_. @@ -340,7 +334,7 @@ docker pull yugabytedb/yugabyte:2.16.6.1-b1 ### Bug fixes -This release includes a [fix for YugabyteDB Anywhere](../../yba-releases/v2.16/#v2.16.6.1) and no changes to YugabyteDB (the core database). +This release includes a [fix for YugabyteDB Anywhere](../v2.16-anywhere/#v2.16.6.1) and no changes to YugabyteDB (the core database). ## v2.16.6.0 - July 20, 2023 {#v2.16.6.0} diff --git a/docs/content/preview/releases/ybdb-releases/v2024.1.md b/docs/content/preview/releases/ybdb-releases/v2024.1.md index e0e85aa079ed..ad14c7c11363 100644 --- a/docs/content/preview/releases/ybdb-releases/v2024.1.md +++ b/docs/content/preview/releases/ybdb-releases/v2024.1.md @@ -25,7 +25,7 @@ YugabyteDB 2024.1.0.0 and newer releases do not support v7 Linux versions (CentO YugabyteDB uses [memory division flags](/stable/reference/configuration/yb-master/#memory-division-flags) to specify how memory should be divided between different processes (for example, [YB-TServer](/stable/architecture/yb-tserver/) versus [YB-Master](/stable/architecture/yb-master/)) on a YugabyteDB node as well as within processes. Using these flags, you can better allocate memory for PostgreSQL, making it more suitable for a wider range of use cases. -For _new_ v2024.1.x universes, if you are expecting to use any nontrivial amount of [YSQL](/stable/api/ysql/), it is strongly recommended to set [ ‑‑use_memory_defaults_optimized_for_ysql](/stable/reference/configuration/yb-tserver/#use-memory-defaults-optimized-for-ysql). This changes the memory division defaults to better values for YSQL usage, and optimizes memory for the node size. +For _new_ v2024.1.x universes, if you are expecting to use any nontrivial amount of [YSQL](/stable/api/ysql/), it is strongly recommended to set [‑‑use_memory_defaults_optimized_for_ysql](/stable/reference/configuration/yb-tserver/#use-memory-defaults-optimized-for-ysql). This changes the memory division defaults to better values for YSQL usage, and optimizes memory for the node size. If you are _upgrading_ a universe, you may want to instead review your memory division settings and adjust them if desired; see [best practices](/stable/develop/best-practices-ysql/#minimize-the-number-of-tablets-you-need). @@ -33,6 +33,169 @@ In future releases, the memory division settings will be used to determine how m {{< /tip >}} +## v2024.1.1.0 - July 31, 2024 {#v2024.1.1.0} + +**Build:** `2024.1.1.0-b137` + +**Third-party licenses:** [YugabyteDB](https://downloads.yugabyte.com/releases/2024.1.1.0/yugabytedb-2024.1.1.0-b137-third-party-licenses.html), [YugabyteDB Anywhere](https://downloads.yugabyte.com/releases/2024.1.1.0/yugabytedb-anywhere-2024.1.1.0-b137-third-party-licenses.html) + +### Downloads + + + +**Docker:** + +```sh +docker pull yugabytedb/yugabyte:2024.1.1.0-b137 +``` + +### Highlights + +**PostgreSQL Logical Replication Protocol Support** {{}} + +We're excited to announce in the 2024.1.1.0 release support for the PostgreSQL Logical Replication Protocol for Change Data Capture (CDC), in addition to the existing native [gRPC Replication protocol](/stable/explore/change-data-capture/using-yugabytedb-grpc-replication/). +This feature allows you to manage CDC streams using [Publications](https://www.postgresql.org/docs/11/sql-createpublication.html) and [Replication Slots](https://www.postgresql.org/docs/current/logicaldecoding-explanation.html#LOGICALDECODING-REPLICATION-SLOTS), similar to native PostgreSQL. Additionally, a [new connector](/stable/explore/change-data-capture/using-logical-replication/get-started/#get-started-with-yugabytedb-connector) is introduced that utilizes the logical replication protocol to consume the CDC streams via [Replication slots](https://www.postgresql.org/docs/current/logicaldecoding-explanation.html#LOGICALDECODING-REPLICATION-SLOTS). + +For more information, refer to [logical replication protocol](/stable/explore/change-data-capture/using-logical-replication/). + +### New features + +- [Automated SQL/CQL Shell binary](/stable/admin/ysqlsh/#installation). Along with full binary, added separate downloadable SQL/CQL Shell binary. + +- [Voyager assessment visualisation in yugabyted UI](/preview/yugabyte-voyager/migrate/assess-migration/#visualize-the-migration-assessment-report). Yugabyted UI provides a dashboard to allow the users to effectively plan the migrations based on the complexity and also be able to monitor the progress of each migration {{}} + +### Change log + +
+ View the detailed changelog + +### Improvements + +#### YSQL + +* Eradicates misleading log message during table creation with DDL atomicity enabled. {{}} +* Removes the unused `keep_order` field from `YbctidGenerator` for cleaner results processing. {{}} +* Updates read time for each operation to simplify code and avoid applying used read time from obsolete operations. {{}} +* Enhances logging for DDL atomicity and corrects a loop index in cross-db unit test for clearer test logs. {{}} + +#### DocDB + +* Offers a new stack trace tracking framework for improved visibility of disk I/O operations, configurable through the `track_stack_traces` gflag. {{}} +* Introduces utility to dump top heap stacks when memory limit is exceeded for enhanced debugging. {{}} +* Adds `SCHECK_PB_FIELDS_NOT_EMPTY` macro for validating non-empty fields, with individual checks on list elements. {{}} +* Disables the unused and unreliable NamespaceReplication tests temporarily for seamless operation. {{}} +* Eliminates potential deadlock issue in DeleteOrHideTabletsAndSendRequests by removing unnecessary shared lock, and introduces a test for bug 22608. {{}} +* Refreshes stack trace tracking UI endpoints to enable per-column sorting and optimize sorting script. {{}} +* Introduces two new `SOURCE_UNREACHABLE` and `SYSTEM_ERROR` enums to enable more detailed error reporting from the Poller. {{}} +* Refreshes stack trace tracking UI endpoints to enable per-column sorting and optimize sorting script. {{}} +* Introduces two new `SOURCE_UNREACHABLE` and `SYSTEM_ERROR` enums to enable more detailed error reporting from the Poller. {{}} +* Shifts tcmalloc profiling code to the Utils folder. {{}} +* Enhances visibility of the `Hidden` state in Master/Tserver Tables UI by shifting its position more prominently to the `State` column. {{}} + +#### CDC + +* Prevents addition of tables with enum array column to the CDC stream to avoid crashes during consumption. {{}} +* Transforms the flag `yb_enable_cdc_consistent_snapshot_streams` from a preview into a default true auto flag. {{}} +* Introduces three new yb-admin commands to remove a user table from a CDCSDK stream, descend dynamic table addition in a CDC stream, and validate CDC state for a particular stream, enhancing control over CDC streams. {{}},{{}} +* Adds a tserver flag, `ysql_yb_default_replica_identity`, for customizing default replica identity at table creation. {{}} +* Introduces `cdcsdk_enable_dynamic_table_addition` flag to manage dynamic table additions in replication slot consumption model. {{}} +* Introduces replication slot name for internal distinction between two consumption models in the code. {{}} +* Allows creating an old model stream via yb-admin in upgraded environments, ensuring only one stream type per database. {{}} +* Eliminates unnecessary NOTICE messages when setting yb_read_time from walsender, reducing message clutter. {{}} + +#### yugabyted + +* Allows to specify multiple data directories using the new `additional_data_dir` configuration. {{}} + +### Bug fixes + +#### YSQL + +* Fixes an error that occurs when decoding null values from a boolean column sorted as NULLS LAST in a secondary index. {{}} +* Fixes YSQL upgrade single connection mode error preventing new connection attempts before the old ones are released. {{}} +* Fixes memory leaks in pg_constraint/pg_attrdef local cache by adding a missing `hash_destroy` call in `YbCleanupTupleCache`. {{}} +* Fixes a memory leak in catalog cache refresh during upgrade that led to higher memory consumption. {{}} +* Resolves remaining memory leaks in CacheMemoryContext to stabilize cache memory after every catalog cache refresh. {{}} +* Stops Batched Nest Loop (BNL) crashes by ensuring better indexing condition checks. {{}} +* Refines the logic to accurately push down join clauses to batched index scans without causing conflicts. {{}} +* Reenables rechecking for RowCompareExpressions to accurately handle NULL inputs in scan bound calculations. {{}} +* Grants BNL hashtable its own expression context to prevent data overwrites during query execution. {{}} +* Allows for an enhanced readability and performance of yb_cost_index code, aiding in merging with the pg15 branch. {{}} +* Fixes a bug in the index tuple width calculation for better YB base scans cost model. {{}} +* Makes `yb_get_range_split_clause` robust using PG TRY CATCH block, ensuring YB backup doesn't fail. {{}} +* Prevents coredumps by ensuring YSQL webserver destruction upon receiving a termination signal. {{}} +* Reduces test iterations of `PgCatalogVersionTest.SqlCrossDBLoadWithDDL` in tsan/asan build to prevent timeouts. {{}} +* Fixes memory leaks in ybcFetchNextHeapTuple by properly freeing the YBCStatus. {{}} +* Replaces `TRUNCATE` with `DELETE FROM` in TestPgTransparentRestarts, enhancing its stability and reducing flakiness. {{}} +* Allows `CreateNamespaceIfNotExists` function to retry on "already exists" error, preventing race conditions. {{}} +* Removes the unused function `Catalocustomeranager::WaitForDdlVerificationToFinish` for clarity. {{}} +* Resolves potential database OID collision with `system_postgres` by excluding reserved OID 65535 in allocation. {{}} +* Prevents the `IN` expressions on single column from wrongly taking the tuple path, ensuring correct data processing. {{}} +* Ensures bitmap scans correctly recheck all results and avoid excluding rows, improving accuracy of outcomes. {{}} +* Fixes incorrect access to the scan plan's bind descriptor during tuple IN condition rechecks. {{}} +* Allows the creation of new shared relations during YSQL upgrade to have a global impact by incrementing the catalog version across every database. {{}} +* Corrects the YbGetOrdinaryColumnsNeedingPgRecheck function to return table column numbers instead of index numbers, preventing unnecessary data fetches and potential crashes or errors after dropping a column. {{}} +* Fixes the issue when a separately created and later attached partition does not properly inherit the parent's primary key using `ALTER TABLE ...ATTACH PARTITION`. {{}} +* Now allows for correct backward prefix-based scanning by eliminating the problematic `kGroupEnd` marker that was leading to inaccurate seek results. {{}} +* Reduces unexpected log messages by not invoking `YsqlDdlTxnCompleteCallback` if all table 'pb_txn_id's in the DDL transaction verifier state are already cleared, avoiding potential deadlock situations in DDL atomicity. {{}} +* Reduces sequence cache collision by incorporating both database and sequence OIDs as the entry key. {{}} +* Resolves a detected deadlock during ALTER TABLE operations, enhancing test stability. {{}} +* Prevents a crash related to memory release associated with TupleTableSlots in SubPlans during a Values Scan. {{}} +* Eliminates the occurrence of "schema version mismatch" error following a DROP INDEX statement by introducing a delay in index deletion. {{}} + +#### DocDB + +* Eliminates possible deadlock during setup replication by fixing the order in which locks are acquired. {{}} +* Removes unnecessary flush during snapshot deletion, preventing write blocks. {{}} +* Resolves a heartbeat metrics issue ensuring full xCluster error information is sent to the new master even during a leader failover, and makes `tserver_heartbeat_metrics_interval_ms` runtime updatable. {{}} +* Converted the `ysql_skip_row_lock_for_update` to an auto-flag to resolve compatibility issues during upgrade, preventing incorrect DB record creations that can affect row visibility and integrity. {{}} +* Prevents duplicate entries in the sequence data filter used by Snapshot schedules, ensuring successful operations. {{}} +* Resolves the issue of `pg_locks` query failure due to missing host node UUID in distributed transactions. {{}} +* Clarifies memory division flags to reflect they are percentage of the process's hard memory limit, not total available memory. {{}} +* Eliminates latency spikes in conflicting workloads by preventing redundant ProbeTransactionDeadlock rpcs. {{}} +* Prevents premature metric destruction during Prometheus scrapes, resolving non-UTF8 character issues. {{}} +* Ensures failed xCluster setup if the xcluster stream state update to `ACTIVE` does not occur. {{}} + +#### CDC + +* Ensures deletion of MemoryContext after each GetChanges RPC to prevent memory leaks. {{}} +* Prevents newly created indexes, materialized views, and non-user tables from being added to the Chang Data Capture (CDC) stream metadata. {{}} +* Reduces resource usage by removing non-eligible tables, like indexes, from existing CDC SDK stream metadata, and releasing retention barriers. This change requires the master flag `enable_cleanup_of_non_eligible_tables_from_cdcsdk_stream` and limits processing to two non-eligible tables per namespace per run with `cdcsdk_table_processing_limit_per_run`. Introduces three yb-admin commands for managing CDC streams. {{}},{{}},{{}} +* Fixes the issue of getting either `0` or a random time as the server's system clock in XLogData from the logical replication stream. {{}} +* Fixes the segmentation fault in walsender for dynamic table addition by refreshing stored replica identities and preventing a race condition when creating dynamic tables. {{}} +* Solves an issue where CDCSDK incorrectly deduces tablets as not interesting for stream before reaching the configured time limit. {{}} +* Refines the logic to remove `BEGIN` record when no DML records are added, preventing potential virtual WAL crashes. {{}} +* Addresses a race condition in dynamic table creation, enhancing stability during table and tablet initialization. {{}} +* Increases timeout for deletion of slot entry from the state table to correct test failures in TSAN builds. {{}} +* Resolves "could not open relation" error by updating slot creation method and simplifying yb_read_time logic. {{}} +* Adds support for data types with dynamic oids in CDC to prevent crashes and allows tables with such columns to join the stream. {{}} + +#### yugabyted + +* Eliminates inconsistent failures in TestSessionParameters.java by resetting roles to default instead of dropping them. {{}} +* Prevents SyntaxWarning and exceptions when incorrect advertise_address is given by adjusting string literals and adding check for errors. {{}},{{}},{{}} + +
+ ## v2024.1.0.0 - June 4, 2024 {#v2024.1.0.0} **Build:** `2024.1.0.0-b129` diff --git a/docs/content/preview/yugabyte-voyager/reference/assess-migration.md b/docs/content/preview/yugabyte-voyager/reference/assess-migration.md index 173a36f47ac4..7d9c5766022f 100644 --- a/docs/content/preview/yugabyte-voyager/reference/assess-migration.md +++ b/docs/content/preview/yugabyte-voyager/reference/assess-migration.md @@ -32,7 +32,7 @@ The valid *arguments* for assess migration are described in the following table: | --iops-capture-interval | Interval (in seconds) at which Voyager will gather IOPS metadata from the source database for the given schema(s).
Default: 120 | | --oracle-db-sid | Oracle System Identifier you can use while exporting data from Oracle instances. Oracle migrations only. | | --oracle-home | Path to set `$ORACLE_HOME` environment variable. `tnsnames.ora` is found in `$ORACLE_HOME/network/admin`. Oracle migrations only. | -| [--oracle-tns-alias](../../yb-voyager-cli/#oracle-options) | TNS (Transparent Network Substrate) alias configured to establish a secure connection with the server. Oracle migrations only. | +| [--oracle-tns-alias](../yb-voyager-cli/#oracle-options) | TNS (Transparent Network Substrate) alias configured to establish a secure connection with the server. Oracle migrations only. | | --send-diagnostics | Enable or disable sending [diagnostics](../../diagnostics-report/) information to Yugabyte.
Default: true
Accepted parameters: true, false, yes, no, 0, 1 | | --source-db-host | Domain name or IP address of the machine on which the source database server is running.
Default: localhost | | --source-db-name | Source database name. | diff --git a/docs/content/stable/architecture/docdb-replication/async-replication.md b/docs/content/stable/architecture/docdb-replication/async-replication.md index 5a27fc3661fa..ee49096eedca 100644 --- a/docs/content/stable/architecture/docdb-replication/async-replication.md +++ b/docs/content/stable/architecture/docdb-replication/async-replication.md @@ -159,12 +159,11 @@ Today, this is done by backing up the source universe and restoring it to the ta Ongoing work, [#17862](https://github.com/yugabyte/yugabyte-db/issues/17862), will replace using backup and restore here with directly copying RocksDB files between the source and target universes. This will be more performant and flexible and remove the need for external storage like S3 to set up replication. - ## Supported deployment scenarios xCluster currently supports active-active single-master and active-active multi-master deployments. -### Active- active single-master +### Active-active single-master Here the replication is unidirectional from a source universe to a target universe. The target universe is typically located in data centers or regions that are different from the source universe. The source universe can serve both reads and writes. The target universe can only serve reads. Since only the nodes in one universe can take writes this mode is referred to as single master. Note that within the source universe all nodes can serve writes. diff --git a/docs/content/v2.20/architecture/docdb-replication/async-replication.md b/docs/content/v2.20/architecture/docdb-replication/async-replication.md index 66a6f5cb10ff..d5f17e08e8de 100644 --- a/docs/content/v2.20/architecture/docdb-replication/async-replication.md +++ b/docs/content/v2.20/architecture/docdb-replication/async-replication.md @@ -159,12 +159,11 @@ Today, this is done by backing up the source universe and restoring it to the ta Ongoing work, [#17862](https://github.com/yugabyte/yugabyte-db/issues/17862), will replace using backup and restore here with directly copying RocksDB files between the source and target universes. This will be more performant and flexible and remove the need for external storage like S3 to set up replication. - ## Supported deployment scenarios xCluster currently supports active-active single-master and active-active multi-master deployments. -### Active- active single-master +### Active-active single-master Here the replication is unidirectional from a source universe to a target universe. The target universe is typically located in data centers or regions that are different from the source universe. The source universe can serve both reads and writes. The target universe can only serve reads. Since only the nodes in one universe can take writes this mode is referred to as single master. Note that within the source universe all nodes can serve writes. diff --git a/docs/data/currentVersions.json b/docs/data/currentVersions.json index b9ac51386077..1ce359688696 100644 --- a/docs/data/currentVersions.json +++ b/docs/data/currentVersions.json @@ -15,9 +15,9 @@ "series": "v2024.1", "alias": "stable", "display": "v2024.1 (STS)", - "version": "2024.1.0.0", - "versionShort": "2024.1.0", - "appVersion": "2024.1.0.0-b129", + "version": "2024.1.1.0", + "versionShort": "2024.1.1", + "appVersion": "2024.1.1.0-b137", "isStable": true, "isSTS": true, "initialRelease": "2024-06-04",