![]() ![]() This would manifest in the logs in messages of the form " unable to dial nXX: breaker open", where XX is the ID of the restarted node. ![]() Fixed a bug causing other nodes in the cluster to fail to connect to a restarted node due to their circuit breakers not resetting after a temporary node outage.Fixed a bug causing a prepared statement to incorrectly reuse the query plan of a different prepared statement that had similar, but not identical type hints.Fixed a bug causing table stats collection issued via an EXPLAIN ANALYZE statement or via a CREATE STATISTICS statement to run into a " flow: memory budget exceeded" error if the statement was executed without specifying the AS OF SYSTEM TIME option.This bug was introduced in version 20.2.0. Fixed a bug that caused internal errors with set operations (e.g., UNION) and columns with tuple types that contained constant NULL values.Changed references to the UI console from "Admin UI" to "DB Console".View a detailed changelog on GitHub: v20.2.16.v20.2.17 DB Console changes $ docker pull cockroachdb/cockroach:v20.2.17 This page lists additions and changes in v20.2.17 since v20.2.16. This release includes 16 merged PRs by 16 authors. Reduced memory usage slightly during ANALYZE or CREATE STATISTICS statements.The bug could only reproduce on tables with at least two multi-column indexes with nullable columns. Fixed a bug which caused incorrect results for some queries that utilized a zig-zag join.Connect timeout for grpc connections is now set to 20s to match the pre-v20.2 default value.Fixed a bug which caused ALTER COLUMN TYPE statements to fail when they should not have.Fixed a panic that could occur with invalid GeoJSON input using ST_GeomFromGeoJSON/ ST_GeogFromGeoJSON.The stack trace (in cockroach-stderr.log) would contain server.(*statusServer).NodesUI in that case. CockroachDB could crash if network connectivity was impaired.CockroachDB now avoids dialing nodes in performance-critical code paths, because doing so could cause substantial latency when encountering unresponsive nodes (e.g., when a VM or server was shut down).Previously, in v21.1.x and earlier, CockroachDB could incorrectly read the data of a unique secondary index that used to be a primary index created via ALTER PRIMARY KEY.Fixed an internal error with joins that are both LATERAL and NATURAL/ USING.Users without the admin role will still see most data about their nodes, but information such as command-line arguments, environment variables, and IP addresses and DNS names of nodes will be hidden. Non- admin users of the DB Console have regained the ability to view the Cluster Overview page.View a detailed changelog on GitHub: v20.2.17.v20.2.18 DB Console changes $ docker pull cockroachdb/cockroach:v20.2.18 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |