Software-update: CockroachDB 23.1.4 / 22.2.11

Het team achter CockroachDB heeft twee nieuwe versies uitgebracht met 23.1.4 en 22.2.11 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 ziet er als volgt uit:

The new sql.auth.createrole_allows_grant_role_membership.enabled cluster setting allows a user with the CREATEROLE role option to grant and revoke non-admin roles. This cluster setting defaults to false, but is expected to become the default behavior in the future. #104445

Fixed an initialization race condition in changefeed schema feeds that could cause a node to crash with a null pointer exception. #104934

Users with MODIFYSQLCLUSTERSETTING can now view only sql.defaults cluster settings instead of all cluster settings. #104542

The debug.zip archive now contains the files formerly located at nodes/*/ranges/*.json in one file per node, nodes/*/ranges.json. #104248The http-defaults and http-servers sections of the log config will now accept a headers field containing a map of key-value string pairs which will comprise custom HTTP headers appended to every request. Additionally, a compression value can now be set to gzip or none to select a compression method for the HTTP request body. By default, gzip is selected. Previous functionality did not compress by default. #104814

The new log config option buffering allows you to format buffer output as JSON arrays. This is useful for APIs that consume JSON arrays, such as the Datadog logs API. #104790

The tenant selection field is now visible only when a user is logged in to more than one non-system tenant. #104819The DB Console overview page now displays a warning when all nodes are running on a new version but the cluster upgrade has not been finalized. #104874The histogram window merge calculation now interpolates quantile values more accurately, and Metrics charts in the DB Console are smoother and more accurate. #104815

Fixed a bug where a transaction retry could miss job rows during the backfill of the Jobs table. #104757Fixed a bug where admin or root user privileges were erroneously required to use SHOW SYSTEM GRANTS. #104732Fixed a bug that prevented display of the column selector on the Jobs page. #104738Fixed a bug where an invalid split could crash and prevent restarts of nodes that hold a replica for the right-hand side. #104850Fixed the debug recover make-plan command to ignore partial range metadata when the metadata can't be fully read, and instead rely solely on replica info from storage to produce the recovery plan. #104774Fixed a metric bug that could cause volumes such as RAID logical volumes to be counted twice.#104806Fixed a bug in upstream etcd-io/raft which could cause an unlimited amount of log to be loaded into memory. This could cause a node to crash with an out-of-memory (OOM) exception. The log scan now has a limited memory footprint. #104968

There is a new server.client_cert_expiration_cache.capacity cluster setting which, when set to a non-zero number, makes it so that the minimum time-until-expiration of the set of client certificates seen is stored (for every user). This setting can be used to ensure client cert expirations are exported as a metric (if set to zero, the metric security.certificate.expiration.client will have a value of zero). #104209

Added a new session variable allow_role_memberships_to_change_during_transaction which can be used to make the granting and revoking of role memberships faster at the cost of some isolation claims. By default, when granting or revoking a role from another role, CockroachDB waits for all transactions that are consulting the current set of role memberships to complete. This means that by the time the transaction which performed the grant or revoke operation returns successfully, the user has a proof that no ongoing transaction is relying on the state that existed prior to the change. The downside of this waiting is that it means that GRANT and REVOKE will take longer than the longest currently executing transaction. In some cases, users do not care about whether concurrent transactions will immediately see the side-effects of the operation, and would instead prefer that the grant or revoke finish rapidly. In order to aid in those cases, the session variable allow_role_memberships_to_change_during_transaction has been added. Now, the grant or revoke will only need to wait for the completion of statements in sessions which do not have this option set. One can set the option as enabled by default in all sessions in order to accelerate and grant and revoke role operations. #103847SHOW GRANTS now lists not just privileges explicitly granted to each role, but also roles which inherit from those. SHOW GRANTS ON ROLE statements no longer require any privileges, and also list implicit grantees. #104589Users with the MODIFYCLUSTERSETTING system-level privilege will no longer be able to view non sql.defaults.* settings if the cluster setting sql.full_modify_cluster_setting.enabled is set to false. #104231