What's new in the v2.5 latest release series
Included here are the release notes for all releases in the v2.5 latest release series.
New release versioning
Starting with v2.2, Yugabyte release versions follow a new release versioning convention. The latest release series, denoted byMAJOR.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. For more information, see Supported and planned releases.
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).Notable features and changes (cumulative for the v2.5 latest release series)
Note: Content will be added as new notable features and changes are available in the patch releases of the v2.5 latest release series. For the latest v2.5 release notes, see Release notes below.
Release notes
Yugabyte Release Notes v2.5.1
Jan 14, 2021
Build: 2.5.1.0-b153
Downloads
Docker
docker pull yugabytedb/yugabyte:2.5.1.0-b153
New features
Yugabyte Platform
- [#5723] Support for custom CA signed certificates for encryption in-flight
- [#5556] Add alerts capability for backup tasks
Core Database
- [#6010] YCQL: Cache authentication information
- [#4874] YSQL: Backup for colocated databases
- [#4899] YSQL: Index backfill unique indexes
- [#6237] YSQL: add CREATE INDEX NONCONCURRENTLY grammar
- [#5982] YSQL: Add support for CREATE TABLE/INDEX ... WITH (table_oid = x)
- [#4770] YSQL: Completing feature RANGE Partitioning
- Improved Clock Skew Handling
- [#6370] Bump default max_clock_skew to 500ms
- [#3335] Crash when too big clock skew is detected
Improvements
Yugabyte Platform
- [#5888] Better error for handling when user creates concurrent backup tasks
- [#6016] Pre-flight checks for create universe / edit universe / add node operations
- [#4183] Add error message for invalid ssh keys for onprem providers
- [#5848] Onprem provider creation failure leaves incomplete state behind
- [#5652] Improve delete universe handling for failed universes
- [#6254] Allow user to input multiple GFlag entries at the same time
- [#4843] New Health check for Replication status in 2dc setup
- [#6268] Utility script to edit universe json from command line
- [#4795] Embed http proxy within yb platform to avoid need for deploying nginx
- [#5799] Delete platform code related to dev/debug package installs and EPEL repo
- [#6228] Enabling Encryption-at-Rest without KMS config causes Create Universe to fail silently
- [#6289] Fixed degraded performance on Live Queries tab caused by huge number of DOM nodes in rows
- [#6383] Disabled unused API endpoint: run_query
- [#6384] Disabled unused API endpoint: run_in_shell
- [#6389] Input validation for kubernetes config path
- [#6386] Added input validation for access_keys API endpoint
- [#6382] Added UI validation for backup target paths
- #6175: Use sudo when removing prometheus snapshots during platform backup
- [#6602] Fix TLS directory while provisioning YB nodes.
- [#6683] Use a timeout mechanism in cluster_health.py that is more compatible with docker's lack of zombie reaping
- [#6633] Platform: rename Pivotal to VMware Tanzu, add Red Hat OpenShift cloud provider
Core Database
- [#6580] ycql: Log the status when statement fails for system query cache
- [#6608, #6609] YCQL: Consolidate authentication error handling and messages
- [YCQL][#6374] Upgrade spark-cassandra-connector version to 2.4-yb-3
- #5678: [YCQL] Optimize updating non-indexed columns within indexed tables.
- [#3329][YSQL] Optimized updates to reflect changes on necessary indexes only
- [#5805] [YSQL] Use slots more widely in tuple mapping code and make naming more consistent
- [YSQL] Clean up libpq connection code (#6481)
- [#6417] [YSQL] Backport 'Skip allocating hash table in EXPLAIN-only mode'
- [#6131] [YSQL] Dowgrade permission check for data directory to warning
- [YSQL] Bubble up backfill error message (#6292)
- [#5805] [YSQL] Don't require return slots for nodes without projection
- [#5805] [YSQL] Split ExecStoreTuple into ExecStoreHeapTuple and ExecStoreBufferHeapTuple
- [#5805] [YSQL] Error position support for defaults and check constraints
- Improvements to 2DC x-cluster async replication
- [#6169] Correctly replay write batches with external intents on bootstrap
- [#6169] New format for external intents
- [#6283] Fix Very Large Metric Lag for 2DC Txns
- [#3522] Fix Threading Issues with CDC Consumer Writes
- [#6068] Replicate Intents and Apply Messages for 2DC Txns
- [#6169] Fix apply order of updated external intents records
- [#4516] 2DC: Initial support for colocated databases
- Improvements to Tooling
- [#6589] docdb: Add option to clear placement info in yb-admin.
- [#6223] master UI make hash_split more readable
- [#6161] Change modify_table_placement_info to wipe read_replicas and affinitized_leaders
- [#5420] ybase: Enhance YMaster admin page to display under-replicated tablets
- [#1325] ybase: API for displaying YB version information
- Improvements to Tablet splitting
- [#4942] docdb: tablet splitting: implemented retries to post-split involved tablets for
- #5937: Fixed the case when one of the tablet replicas is down during the split.
- #6101 Add the flag to limit number of tablets per table
- [#6424] Fix post-split compaction to be async
- Improvements to core product security
- [#6568] Add flag to force client certificate verification in SSL
- [#6266] Replace retry counter with check that data is ready
- [#6266] Retry SSL_write on SSL_ERROR_WANT_WRITE
- [#6266] Fix handling SSL_write error
- [#6394, #6434] docdb: Speedup system.partitions queries
- [#3979] Add Transaction Cleanup to Catalog Manager Create DDLs
- [#1258]: Send election request from master during table creation
- [#6114] docdb: Add metrics for master YCQL system table
- [#1259] Speedup DROP TABLE
- [#5752] Avoid starving threadpool with run election tasks from FailureDetector
- [#5755] Faster cleanup of transactions that failed to commit due to a concurrent abort
- (#5996) Messenger::ScheduleOnReactor should break loop finding reactor
- [#6305] Adaptive Heartbeat Reporting
- [#6445] docdb: Master should rebuild YCQL system.partitions on a background thread
- [#6696] Small master perf tweaks
Bug Fixes
Yugabyte Platform
- [#6300] Install of s3cmd fails for default GCP OS image when airgapped
- [#6085] Fixed the issue where master is brought up in read replica cluster
- [#6416] Deletion with flag --node_ip fails for onprem universes.
- [#6614] Fixed NPE with full move
- [#6252] Fixed NPE on the metrics page
- [#5942] Fixed an issue where release instance is not an option for a node should the install fail because of ssh access
- [#6275] Fixed missing stats on Nodes page when universe has read replicas
- [#6257] Updating user profile when smtp username or password are empty
Core Database
-
[#6144] YCQL: Fix handling of tablet-lookup errors in Executor::FlushAsync
-
[#6570] YSQL: Use IsYBRelation instead of IsYugaByteEnabled
-
[#6492] YSQL Avoid memcpy() with a NULL source pointer and count == 0
-
[YSQL] Fix IsCreateTableDone for index backfill (#6234)
-
[#6318, #6334] Call InitThreading in YSQL webserver process
-
#6317: [YSQL] Fixed SIGSERV in YBPreloadRelCache
-
[#6364] [YSQL] Replace CurrentMemoryContext with GetCurrentMemoryContext for all pg_extensions
-
#6219] [YSQL] PRIMARY KEY index in TEMP TABLE is not checked for uniqueness
-
(#6284) [YSQL] Clear ALTERING when there's no alter
-
[#5805] [YSQL] Fix run-time partition pruning for appends with multiple source rels
-
[#6151] [YSQL] Handle rowmark in case of read with batch of ybctids
-
(#6270) [YSQL] Prevent concurrent backfill index
-
[#6133] [YSQL] Fix procedure with an INOUT parameter in DO block
-
[#6061] [YSQL] ysql_dump should consistently use quotes on column names
-
#6009: [backup][YSQL] Fixed incorrect column-ids in restored YSQL table if original table was altered.
-
#5954 [YSQL] Check transaction status after read finished
-
#6430 [YSQL] Refresh YBCache in case postgres clears its internal cache
-
#6468 [YSQL] Fix read restarts of request with paging state
-
[#6435] docdb: fixed handling of empty bloom filter key in the write path
-
[#6435] Fixed bloom filter index generation for range-partitioned tablets
-
[#6375] Check against TabletPeer returning null tablet pointer in
-
(#5641) Fix for --cert_node_filename for tservers and --enable_ysql
-
[#6318, #6334] Call InitThreading in YSQL webserver process
-
[#4150] Fix incorrect tracking of flushed/synced op id in case of Raft operation abort
-
(#6278) Master SEGV during LB due to null TSDescriptor
-
[#6353] Disable rocksdb flush on all DeleteTablet calls
-
[#6338] Fix crash with redis workloads and snapshot restore
-
[#6334] Attach/detach Squeasel threads to/from libcds using callbacks
-
[#6245] Fixed incorrect restored table schema if the table was altered after the backup.
-
[#6217] Avoid a possible assertion failure in CDSAttacher destructor in Webserver
-
[#6170] Shutdown status resolver before destroying it in ResolveIntents
-
[#6482] Fix timeout handling when getting safe time in a RF1 cluster
-
[#6635] Fix the wrong detection of communication failure when no operations transferred
-
[#6678] backup: Fix restore of colocated table with table_oid already set
Known Issues
Yugabyte Platform
- Azure IaaS orchestration
- No pricing information provided (5624)
- No support for regions with zero Availability Zones(AZs) (5628)
Core Database
- Advisory on clock-skew
- After commit
a60a4ae00d217563cac865b3363e2c2bb8aa58ba
, by default, any YB node will explicitly crash if it detects a clock skew higher than themax_clock_skew
flag (default 500ms). This can be disabled by settingfail_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.
- After commit
v2.5.0 - November 12, 2020
Build: 2.5.0.0-b2
Downloads
Docker
docker pull yugabytedb/yugabyte:2.5.0.0-b2
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 Yugabyte Master and 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 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:
- Online rebuild of indexes 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 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 forpg_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 can now be performed with commands such as
EXPLAIN
andEXPLAIN 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-prem deployment workflows
- Do not fail universe creation if cronjobs can't be created for on-prem (5939)
- Remove pre-provision script requirement for air-gapped installations (5929)
- "Sudo passwordless" in on-prem 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)
- Prometheus 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)
- Yugabyte Platform now provides alerts for backup tasks (5556)
- 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-prem provider (5550)
- Update backup target and backup pages (5917)
- For Yugabyte 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)
- 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 tserver gflag
ysql_sequence_cache_minval
(6041) - Added compatibility mode in the yb_backup script for Yugabyte version < 2.1.4 (5810)
- Stability improvements: Make exponential backoff on lagging RAFT followers send NOOP instead of reading 1 op from disk (5527)
- Added use of separate metrics objects for RegularDB and IntentsDB (5640)
Bug Fixes
Yugabyte Platform
- Fix for Universe disk usage shows up empty on the universe page (5548)
- Fix on on-prem 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 Yugabyte TServer Node when another Yugabyte Master node is down in the Universe (5739)
- Use the correct disk mount point while calculating disk usage of logs (5983)
- Fixes to delete backups for TLS Enabled Universes (5980)
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 column(s) (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 YB Platform when there are Read Replicas. This fix will ignore read replica TServers when running AreLeadersOnPreferredOnly (6081)
- Fixes to restore of YSQL Backups after dropping and recreating a database (5651)
- Fixes to 2DC(x-cluster replication) by adding TLS support for cleaning up cdc_state table (5905)
Known Issues
Yugabyte Platform
- Azure IaaS orchestration -
- No pricing information provided (5624)
- No support for regions with zero Availability Zones(AZs) (5628)