docs/content/stable/releases/ybdb-releases/end-of-life/v2.4.md
Included here are the release notes for all releases in the v2.4 release series. Content will be added as new notable features and changes are available in the patch releases of the v2.4 release series.
{{< warning title="Use v2.4.4.0 or later" >}}
YugabyteDB version 2.4.4.0 contains an important fix for a bug in a downstream dependency (the gperftools package). This tcmalloc memory allocation bug could lead to process crashes. If you're using a version higher than 2.4.0.0, please upgrade as soon as possible.
Refer to issue 8531 for details.
This bug does not affect version 2.4.0.0.
{{< /warning >}}
Build: 2.4.8.0-b16
docker pull yugabytedb/yugabyte:2.4.8.0-b16
Build: 2.4.7.0-b7
docker pull yugabytedb/yugabyte:2.4.7.0-b7
N/A
docker pull yugabytedb/yugabyte:2.4.6.0-b10
docker pull yugabytedb/yugabyte:2.4.5.0-b20
N/A
docker pull yugabytedb/yugabyte:2.4.4.0-b7
N/A
docker pull yugabytedb/yugabyte:2.4.3.0-b6
[1342] Fixing the error message when the get host info call to gcp fails
[8165] Yugabyte Platform (YugaWare) creates zombie ssh process
[8150] [8196] Fix preceding op id in case of empty ops sent to the follower
[8348] Correctly handling a failure to create a priority thread pool worker thread
docker pull yugabytedb/yugabyte:2.4.2.0-b45
docker pull yugabytedb/yugabyte:2.4.1.1-b4
docker pull yugabytedb/yugabyte:2.4.1.0-b25
table_oid already set [6678]ysql_dump when backing up a node-to-node TLS-enabled universedocker pull yugabytedb/yugabyte:2.4.0.0-b60
Data encryption in-transit enhancements:
Moving of TLS In-Transit Certificates to Cloud > Security Config
Support for Rolling restart of a universe (6323)
Support for VMware Tanzu as a new cloud provider (6633)
Alerts for backup tasks (5556)
Support for Transactional tables and Cross Cluster Async Replication topology (5779)
Support for very large transactions and stability improvements (1923)
Displaying an entire query in the detailed view of the live queries tab (6412)
Not returning Hashes and Tokens in API responses (6388)
Authentication of proxy requests against a valid platform session (6544)
Disabling of the unused API endpoint run_query (6383)
Improved error handling for user-created concurrent backup tasks (5888)
Performance improvements for live queries (6289)
Pre-flight checks for Create Universe, Edit Universe, and Add Node operations for an on-premise provider (6016)
Disabling of the unused API endpoint run_in_shell (6384)
Disabling of the unused API endpoint create_db_credentials (6385)
Input validation for Kubernetes configuration path (6389)
Input validation for the access_keys API endpoint (6386)
Input path validation for backup target paths (6382)
Timeout support for busybox (6652)
Enabling of CORS policy by default (6390)
Deleting backups for TLS-enabled universes (5980)
ALTER versions for ORM support (4424)
SQL support improvements:
Performance improvements:
YSQL usability improvements:
YSQL statement execution statistics (5478)
Improved raft leader stepdown operations, by waiting for the target follower to catch up. This reduces the unavailability window during cluster operations. (5570)
Improved performance during cluster overload:
Improved performance for YCQL and many connections:
Improved DNS handling:
Improved master-level load balancer (LB) operations:
Skip loading deleted table metadata into master memory (5122)
Critical fixes for transaction cleanup applicable to aborted transactions (observed frequently as servers reaching soft memory limit)
Main raft fixes:
Metrics reporting could be inconsistent due to regular and intent rocksdb using the same statistics object (5640)
Various issues with the rocksdb snapshot mechanism used for backup/restore (6170,4756,5337)
Fixes in the YCQL API:
Fixes in the YSQL API:
Retry on SSL_ERROR_WANT_WRITE (6266)
Azure IaaS orchestration (in beta status):
Automatic Tablet Splitting:
{{< note title="New release versioning" >}}
Starting with v2.2, Yugabyte release versions follow a new release versioning convention. The preview release series, denoted by MAJOR.ODD, incrementally introduces new features and changes and is intended for development and testing only. Revision releases, denoted by MAJOR.ODD.REVISION versioning, can include new features and changes that might break backwards compatibility.
{{< /note >}}
{{< note title="Upgrading from 1.3" >}}
Prior to v2.0, YSQL was still in beta. Upon release of v2.0, a backward-incompatible file format change was made for YSQL. For existing clusters running pre-2.0 release with YSQL enabled, you cannot upgrade to v2.0 or later. Instead, export your data from existing clusters and then import the data into a new cluster (v2.0 or later).
{{< /note >}}