Software-update: CockroachDB 23.1.3 / 22.1.21

Het team achter CockroachDB heeft twee nieuwe versies uitgebracht met 23.1.3 en 22.1.21 als de versienummers. Dit is een opensourcedatabase die uitermate geschikt is voor cloudomgevingen en die verschillende opties voor het opvangen van problemen in de bijbehorende verspreide data biedt. Voor meer informatie verwijzen we naar deze pagina, waar de meest gestelde vragen worden beantwoord. De lijst met aanpassingen van deze uitgaves zien er als volgt uit:

View a detailed changelog on GitHub: v23.1.2...v23.1.3

The new server.client_cert_expiration_cache.capacity cluster setting allows you to configure the minimum time until a user's set of client certificates will expire. When server.client_cert_expiration_cache.capacity is set to a non-zero value, the new metric security.certificate.expiration.client tracks the number of client certificates that have expired. #104165

Role-based audit logging is now an Enterprise feature. Only Enterprise users will be able to configure role-based audit logging using the sql.log.user_audit cluster setting. #104453The new sql.log.user_audit cluster setting enables role-based auditing. When the setting is enabled, you can set an audit logging configuration using a table-like syntax. Each row in the configuration represents an audit setting in the configuration. An audit setting is comprised of the following columns: USER/ROLE and STATEMENT_FILTER:SET CLUSTER SETTING sql.log.user_audit = ' test_role ALL another_role NONE ALL NONE';#104179Introduced the sql.log.user_audit.reduced_config.enabled cluster setting. When enabled, this cluster setting computes a "reduced" audit configuration based on the user's current role memberships and the current value for the sql.log.user_audit cluster setting. The "reduced" audit configuration is computed at the first SQL event emit by the user, after the setting is enabled. When the cluster setting is enabled, CockroachDB can compute the audit configuration once at session start, which provides around a 5% increase in throughput. However, changes to the audit configuration (user role memberships or cluster setting configuration) are not reflected within a session. A new session should be started to reflect the configuration changes in auditing behavior. #104372

When the sql.trace.stmt.enable_threshold or sql.trace.txn.enable_threshold cluster settings is enabled, the logging output is now emitted on the SQL_EXEC channel. Previously, this was emitted to the DEV channel. #104047SHOW GRANTS now lists privileges inherited by role membership. SHOW GRANTS ON ROLE statements no longer require any privileges and also lists implicit grantees. #104587

The new metric leases.liveness shows the number of liveness range leases per node to track the liveness range leaseholder. #104076The new a gauge metric sql.conns_waiting_to_hash counts the number of connection attempts that are being limited due to the number of concurrent password hashing operations. This behavior has been present since v21.2 to prevent password hashing from increasing CPU load. The metric is expected to be 0, or close to 0, in a healthy setup. If the metric is consistently high and connection latencies are high, then an operator should do one or more of the following:Ensure applications using the cluster have properly configured connection pools.Add more vCPU or more nodes to the cluster.Increase the password hashing concurrency using the COCKROACH_MAX_PW_HASH_COMPUTE_CONCURRENCY environment variable. #104388

Ensure applications using the cluster have properly configured connection pools.Add more vCPU or more nodes to the cluster.Increase the password hashing concurrency using the COCKROACH_MAX_PW_HASH_COMPUTE_CONCURRENCY environment variable. #104388

Added merge queue failure and merge queue processing time metrics to the Queue Processing Failures and Queue Processing Times graphs respectively. #104034Removed the Circuit Breaker Tripped Events graph from the Replication dashboard. #104038Added Completed time to Jobs and Job details pages, and updated the time format on those pages to include seconds and milliseconds. #104063Added a Created SQL Connections chart on the SQL dashboard under Metrics. #104072Added Ranges in Catchup Mode and Rangefeed Catchup Scans Duration charts to the Changefeeds dashboard. #104122The sort setting on the Hot Ranges page is now persisted across page reloads and navigation. #104112The Databases page now supports a large number of tables for a single database. If more than 40 tables are present in a database, the sort on the page will be disabled; however, it is still possible to filter by table name. #103854On the Statement Details page, renamed the "Idle Latency" metric to "Client Wait Time" and separated it into its own chart. #103915Added more search criteria options on the SQL Activity page:For the Top dropdown: 1000, 5000, and 10000.For the By dropdown on the Statements tab: Last Execution Time, Max Latency, Max Memory, Min Latency, Network, P50 Latency, P90 Latency, Retries, and Rows Processed.For the By dropdown on the Transactions tab: Max Memory, Network, Retries, and Rows Processed. #104054Added a new link to the Range Status page on the Replication dashboard that opens the Enqueue Ranges page with the node ID already completed. #104100The DB Console will no longer show DROP INDEX recommendations for unique indexes. #104287On the Transactions tab of the SQL Activity page, the Status will be Idle if the executing transaction is not currently executing a statement. Previously, the status would be Executing. #103925Fixed the job that updates the statement_activity and transaction_activity tables on the SQL Activity page. The table size is now constrained when there are a lot of unique queries. This fix helps to prevent slowing down the SQL Activity page. #104340