yugabyte/yugabyte-db v2.5.0

2.5.0.0 (Released Nov 12, 2020)

on GitHub

New features

Yugabyte Platform

• 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 YB-Master and YB-TServer process. (5831)

Core database

• 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
  This allows 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
  This is 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:

• Online rebuild of indexes
  This is supported for both the YSQL and YCQL APIs. This means that new indexes can be added to tables with pre-existing data while concurrent updates are happening on the cluster. The online index rebuild process creates the newly added index in the background, and transactionally enables the index once the rebuild of all the data is completed. This feature allows flexibility of adding indexes as the application needs evolve to keep queries efficient.

• Cluster execution statistics and running queries
  This can be analyzed in detail, allowing administrators to gain insights into how the database is performing. The pg_stat_statements extension, which enables tracking execution statistics of all SQL statements executed by the cluster, is supported and enabled by default. Support for pg_stat_activity has also been added, which shows information related to the activity performed by each connection. Yet another useful feature in this category is the ability to view all the live queries being executed by the cluster at any point in time.

• Detailed query plan and execution analysis
  This can now be performed with commands such as EXPLAIN and EXPLAIN ANALYZE. These commands display the execution plan generated by the planner for a given SQL statement. The execution plan shows details for any SQL statement such as how tables will be scanned (plain sequential scan, index scan), what join algorithms will be used to fetch required rows from the different tables, etc.

Improvements

Yugabyte Platform

• Enhancements to on-premises deployment workflows:
  • Do not fail universe creation if cronjobs can't be created for on-premises. (5939)
  • Remove pre-provision script requirement for airgapped installations. (5929)
  • "Sudo passwordless" in on-premises cloud provider configuration toggle is renamed.
  • Allow yugabyte user to belong to other user groups in Linux. (5943)
  • Added a new "Advanced" section in on-prem cloud provider configuration which includes:
    • Use hostnames
    • Desired home directory
    • Node exporter settings
  • Improvements to installation of Prometheus Node Exporter utility workflow. (5926)
    • The node exporter option is now available in the cloud configuration under advanced settings.
    • Supports bringing your own node exporter user.
• Make YEDIS API optional for new Universes and no change in behavior of existing universes. (5207)
• UI/UX improvements for YB Platform:
  • Add visual feedback when backup or restore is initiated from modal. (5908)
  • Minor fixes to primary cluster widget text issue. (5988)
  • Show pre-provision script in UI for non-passwordless sudo on-premises provider. (5550)
  • Update backup target and backup pages. (5917)
• For YugabyteDB universes with replication factor (RF) > 3, change the default min_num replicas for even distribution of AZs across all regions. (5426)
• Added functionality to create IPv6-enabled universe in Kubernetes. (5309, 5235)

Core database

• Support for SQL/JSON Path Language (jsonb_path_query). (5408)
• Remove range-loop-analysis and fallthrough errors in our code. (5812)
• Incorrect index update if used expression result is still unchanged. (5898)
• As part of the tablet splitting feature:
  • Implemented cleanup of the tablet for which all replicas have been split for. (4929)
  • Compaction improvements (5523)
• Improve performance for sequences by using higher cache value by default. Controlled by a YB-TServer configuration flag --ysql_sequence_cache_minval. (6041)
• Added compatibility mode in the yb_backup.py script for YugabyteDB version earlier than v2.1.4. (5810)
• Stability improvements to core database - make exponential backoff on lagging RAFT followers send NOOP. (5527)
• Added use of separate metrics objects for RegularDB and IntentsDB. (5640)
• Improvements to 2DC (xCluster replication) by adding TLS support for cleaning up cdc_state table. (5905)

Bug fixes

Yugabyte Platform

• Fix for Universe disk usage shows up empty on the universe page. (5548)
• Fix on on-premises backup failures due to file owned by the root user. (6062)
• Fix for a bug where user operation to perform a change to nodes count by AZ was doing a full move. (5335)
• Fixes for Yugabyte Platform data backup script for Replicated-based installations
• Fixes to Client Certificate start time to use UTC during download. (6118)
• Fixes for migration if no access keys exist yet. (6099)
• Fix to resolve issues caused by starting a YB-TServer node when another YB-Master node is down in the universe. (5739)
• Use the correct disk mount point while calculating disk usage of logs. (5983)

Core database

• Fix for bug with the duplicate row detection that allows a unique index to get created when the table is not unique on the index columns. (5811)
• Improve fault tolerance of DDLs and reduce version mismatch errors in YSQL. (3979, 4360)
• Fixes to incorrect column-ids in the restored table if the original table was altered. (5958)
• Fixes timeout bug in Yugabyte Platform when there are read replicas. This fix will ignore read replica YB-TServers when running AreLeadersOnPreferredOnly. (6081)
• Fixes to restore of YSQL Backups after dropping and recreating a database. (5651)
• Fixes to a bug with the duplicate row detection that allows a unique index to get created when the table is not unique on the index columns. This is fixed by setting the read time for backfill write requests to be the safe time chosen for backfill read requests rather than the hard-coded time 50. (5811)
• Fixes to delete backups for TLS-enabled universes. (5980)

Known Issues

Yugabyte Platform

• Azure IaaS orchestration:
  • No pricing information provided. (5624)
  • No support for regions with zero availability zones (AZs). (5628)