docs/content/stable/releases/ybdb-releases/end-of-life/v2.5.md
{{< warning title="Use v2.5.3.4 or later" >}}
YugabyteDB version 2.5.3.4 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 previous 2.5 version, please upgrade as soon as possible.
Refer to issue 8531 for details.
{{< /warning >}}
Build: 2.5.3.4-b1
docker pull yugabytedb/yugabyte:2.5.3.4-b1
Build: 2.5.3.1-b10
docker pull yugabytedb/yugabyte:2.5.3.1-b10
7493 Menu shows 0 appended to "Upgrade Software0" when there is nothing to upgrade. When the universe is up-to-date (in other words, there are no upgrades available), the Action menu shows "Upgrade Software0". This is a cosmetic bug, and will be addressed in a future release.
Build: 2.5.2.0-b104
docker pull yugabytedb/yugabyte:2.5.2.0-b104
Build: 2.5.1.0-b153
docker pull yugabytedb/yugabyte:2.5.1.0-b153
a60a4ae00d217563cac865b3363e2c2bb8aa58ba, by default, any YB node will explicitly crash if it detects a clock skew higher than the max_clock_skew flag (default 500ms). This can be disabled by setting fail_on_out_of_range_clock_skew=false, but this could lead to consistency issues! The recommendation is that you ensure clocks are synchronized across your cluster.Build: 2.5.0.0-b2
docker pull yugabytedb/yugabyte:2.5.0.0-b2
Azure Cloud integration for Yugabyte Platform (in beta):
Yugabyte Platform is natively integrated with Azure cloud to simplify deploying, monitoring, and managing YugabyteDB deployments. This feature automates a number of operations including orchestration of instances, secure deployments, online software upgrades, and scheduled backups, as well as monitoring and alerting. (6094, 6020)
Yugabyte Platform operations now allow promoting a Yugabyte TServer only node to run Yugabyte Master and TServer process (5831)
Enhanced multi-region capabilities with geo-partitioning and follower reads
The YugabyteDB 2.5 release adds row-level geo-partitioning capabilities as well as follower reads to the extensive set of multi-region features that YugabyteDB already had.
Enterprise-grade security features:
Authentication using the highly secure SCRAM-SHA-256 is now supported to limit security risks from brute force attacks and sniffing, including LDAP support for better user management and the ability to audit all database operations.
Table-level partitions allow users to split what is logically one large table into smaller sub-tables, using the following types of table partitioning schemes that PostgreSQL supports: range partitioning, list partitioning, and hash partitioning. Read more about table partitioning in YugabyteDB.
Event triggers are now supported in addition to regular table-level triggers in YSQL. While regular triggers are attached to a single table and capture only DML events, event triggers are global to a particular database and are capable of capturing DDL events. The event-based trigger framework enables detecting changes made to the data, and automating any subsequent tasks that need to be performed, which are useful in a number of use cases such as implementing a consolidated, central audit table (2379)
Simplified cluster administration:
ysql_sequence_cache_minval (6041){{< 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 >}}