diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml index 1550c7ecc64..f28730ac778 100644 --- a/src/current/_data/releases.yml +++ b/src/current/_data/releases.yml @@ -6861,3 +6861,37 @@ docker_arm_experimental: false docker_arm_limited_access: false source: true + +- release_name: v23.1.28 + major_version: v23.1 + release_date: '2024-10-10' + release_type: Production + go_version: go1.22.5 + sha: 76e598c9b1c100fd9280b979140b5e377c330a20 + has_sql_only: true + has_sha256sum: true + mac: + mac_arm: true + mac_arm_experimental: true + mac_arm_limited_access: true + windows: true + linux: + linux_arm: true + linux_arm_experimental: false + linux_arm_limited_access: false + linux_intel_fips: true + linux_arm_fips: false + docker: + docker_image: cockroachdb/cockroach + docker_arm: true + docker_arm_experimental: false + docker_arm_limited_access: false + source: true + previous_release: v23.1.27 + cloud_only: true + cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters' + cloud_only_message: > + This version is currently available only for select + CockroachDB Cloud clusters. To request to upgrade + a CockroachDB self-hosted cluster to this version, + [contact support](https://support.cockroachlabs.com/hc/requests/new). \ No newline at end of file diff --git a/src/current/_includes/common/network-partitions.md b/src/current/_includes/common/network-partitions.md new file mode 100644 index 00000000000..efd07128306 --- /dev/null +++ b/src/current/_includes/common/network-partitions.md @@ -0,0 +1,7 @@ +A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is [drained and restarted]({% link {{ page.version.version }}/node-shutdown.md %}). + +In a **symmetric** partition, node communication is disrupted in both directions. In an **asymmetric** partition, nodes can communicate in one direction but not the other. + +CockroachDB protects against asymmetric partitions by converting all asymmetric (uni-directional) network partitions into symmetric (bi-directional) network partitions. This increases cluster resiliency by reducing the number of partition-related failures that can occur. Many temporary symmetric partitions can be recovered from automatically without operator intervention. + +The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) or [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) are defined. A partition that cuts off at least `(n-1)/2` replicas from a [range]({% link {{ page.version.version }}/architecture/overview.md %}#architecture-range) will cause range unavailability which will cause some data unavailability. If there are no localities or other constraints on where replicas are placed, then a partition of any ([`num_replicas`]({% link {{ page.version.version }}/configure-replication-zones.md %}#num_replicas) / 2) nodes will likely cause unavailability. diff --git a/src/current/_includes/releases/v23.1/v23.1.28.md b/src/current/_includes/releases/v23.1/v23.1.28.md new file mode 100644 index 00000000000..bc5cec92d70 --- /dev/null +++ b/src/current/_includes/releases/v23.1/v23.1.28.md @@ -0,0 +1,51 @@ +## v23.1.28 + +Release Date: October 10, 2024 + +{% include releases/new-release-downloads-docker-image.md release=include.release %} +

General changes

+ +- Upgraded [gRPC]({% link v23.1/architecture/distribution-layer.md %}#grpc) to v1.56.3. [#130044][#130044] + +

Operational changes

+ +- Added the `ranges.decommissioning` metric that represents the number of [ranges]({% link v23.1/architecture/glossary.md %}#range) which have a [replica]({% link v23.1/architecture/glossary.md %}#replica) on a [decommissioning node]({% link v23.1/node-shutdown.md %}). [#130254][#130254] + +

DB Console changes

+ +- DB Console will show an alert message when the [license]({% link v23.1/licensing-faqs.md %}) is expired or there are less than 15 days left before it expires. [#130439][#130439] +- DB Console will show a notification alerting customers without an Enterprise [license]({% link v23.1/licensing-faqs.md %}) to upcoming license changes with a link to more information. [#130439][#130439] + +

Bug fixes

+ +- Fixed a bug where the [`schema_locked` table parameter]({% link v23.1/with-storage-parameter.md %}#table-parameters) did not prevent a table from being referenced by a [foreign key]({% link v23.1/foreign-key.md %}). [#129752][#129752] +- Fixed a bug where the [`require_explicit_primary_keys`]({% link v23.1/session-variables.md %}#require-explicit-primary-keys) session variable would overly aggressively prevent all [`CREATE TABLE`]({% link v23.1/create-table.md %}) statements from working. [#129905][#129905] +- Fixed a rare bug where a [lease transfer]({% link v23.1/architecture/replication-layer.md %}#epoch-based-leases-table-data) could lead to a `side-transport update saw closed timestamp regression` panic. The bug could occur when a node was [overloaded]({% link v23.1/ui-overload-dashboard.md %}) and failing to heartbeat its [node liveness]({% link v23.1/cluster-setup-troubleshooting.md %}#node-liveness-issues) record. [#130124][#130124] +- Fixed a slow-building memory leak when using [Kerberos authentication]({% link v23.1/gssapi_authentication.md %}). [#130316][#130316] [#130820][#130820] +- Resolve a log message that read: `expiration of liveness record ... is not greater than expiration of the previous lease ... after liveness heartbeat`. This message is no longer possible. [#130623][#130623] +- Fixed a potential memory leak in [changefeeds]({% link v23.1/change-data-capture-overview.md %}) using a [cloud storage sink]({% link v23.1/changefeed-sinks.md %}#cloud-storage-sink). The memory leak could occur if both `changefeed.fast_gzip.enabled` and `changefeed.cloudstorage.async_flush.enabled` are `true` and the changefeed received an error while attempting to write to the cloud storage sink. [#130613][#130613] + +

Miscellaneous

+ +

Security fix

+ +- SHOW CHANGEFEED JOB, [SHOW CHANGEFEED JOBS]({% link v23.1/show-jobs.md %}#show-changefeed-jobs), and [SHOW JOBS]({% link v23.1/show-jobs.md %}) no longer expose user sensitive information like `client_key`. [#129910][#129910] + + +[#128068]: https://github.com/cockroachdb/cockroach/pull/128068 +[#129752]: https://github.com/cockroachdb/cockroach/pull/129752 +[#129905]: https://github.com/cockroachdb/cockroach/pull/129905 +[#129910]: https://github.com/cockroachdb/cockroach/pull/129910 +[#130044]: https://github.com/cockroachdb/cockroach/pull/130044 +[#130124]: https://github.com/cockroachdb/cockroach/pull/130124 +[#130254]: https://github.com/cockroachdb/cockroach/pull/130254 +[#130316]: https://github.com/cockroachdb/cockroach/pull/130316 +[#130439]: https://github.com/cockroachdb/cockroach/pull/130439 +[#130613]: https://github.com/cockroachdb/cockroach/pull/130613 +[#130623]: https://github.com/cockroachdb/cockroach/pull/130623 +[#130689]: https://github.com/cockroachdb/cockroach/pull/130689 +[#130816]: https://github.com/cockroachdb/cockroach/pull/130816 +[#130820]: https://github.com/cockroachdb/cockroach/pull/130820 +[038cda982]: https://github.com/cockroachdb/cockroach/commit/038cda982 +[7f4a0e989]: https://github.com/cockroachdb/cockroach/commit/7f4a0e989 +[d5a2b0d4a]: https://github.com/cockroachdb/cockroach/commit/d5a2b0d4a diff --git a/src/current/v23.1/cluster-setup-troubleshooting.md b/src/current/v23.1/cluster-setup-troubleshooting.md index 05f71f37c59..8cd2c039632 100644 --- a/src/current/v23.1/cluster-setup-troubleshooting.md +++ b/src/current/v23.1/cluster-setup-troubleshooting.md @@ -232,9 +232,9 @@ Again, firewalls or hostname issues can cause any of these steps to fail. If the DB Console lists any dead nodes on the [**Cluster Overview** page]({% link {{ page.version.version }}/ui-cluster-overview-page.md %}), then you might have a network partition. -**Explanation:** A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other. +**Explanation:** -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} **Solution:** diff --git a/src/current/v23.1/ui-network-latency-page.md b/src/current/v23.1/ui-network-latency-page.md index 413e570f1f0..e892a7d3e95 100644 --- a/src/current/v23.1/ui-network-latency-page.md +++ b/src/current/v23.1/ui-network-latency-page.md @@ -35,11 +35,7 @@ For instance, the cluster shown above has nodes in `us-west1`, `us-east1`, and ` Nodes that have lost a connection are displayed in a separate color. This can help you locate a network partition in your cluster. -{{site.data.alerts.callout_info}} -A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other. - -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. -{{site.data.alerts.end}} +{% include common/network-partitions.md %} Click the **NO CONNECTIONS** link to see lost connections between nodes or [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality), if any are defined. diff --git a/src/current/v23.2/cluster-setup-troubleshooting.md b/src/current/v23.2/cluster-setup-troubleshooting.md index 00b103b17ff..b56d59142fc 100644 --- a/src/current/v23.2/cluster-setup-troubleshooting.md +++ b/src/current/v23.2/cluster-setup-troubleshooting.md @@ -232,9 +232,9 @@ If the DB Console then you might have a network partition. -**Explanation:** A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. +**Explanation:** -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} **Solution:** diff --git a/src/current/v23.2/ui-network-latency-page.md b/src/current/v23.2/ui-network-latency-page.md index 8ed8b1c870a..e42b6ea77a4 100644 --- a/src/current/v23.2/ui-network-latency-page.md +++ b/src/current/v23.2/ui-network-latency-page.md @@ -57,9 +57,7 @@ Hover over a cell to display more details: This specific information can help you understand the root cause of the connectivity issue. {{site.data.alerts.callout_info}} -A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. - -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} {{site.data.alerts.end}} ### Node liveness status diff --git a/src/current/v24.1/cluster-setup-troubleshooting.md b/src/current/v24.1/cluster-setup-troubleshooting.md index 1319c80d142..ec659cc2bcf 100644 --- a/src/current/v24.1/cluster-setup-troubleshooting.md +++ b/src/current/v24.1/cluster-setup-troubleshooting.md @@ -232,9 +232,9 @@ If the DB Console then you might have a network partition. -**Explanation:** A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. +**Explanation:** -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} **Solution:** diff --git a/src/current/v24.1/ui-network-latency-page.md b/src/current/v24.1/ui-network-latency-page.md index 864ad9f4407..1206f4659b3 100644 --- a/src/current/v24.1/ui-network-latency-page.md +++ b/src/current/v24.1/ui-network-latency-page.md @@ -57,9 +57,7 @@ Hover over a cell to display more details: This specific information can help you understand the root cause of the connectivity issue. {{site.data.alerts.callout_info}} -A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. - -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} {{site.data.alerts.end}} ### Node liveness status diff --git a/src/current/v24.2/cluster-setup-troubleshooting.md b/src/current/v24.2/cluster-setup-troubleshooting.md index 1319c80d142..ec659cc2bcf 100644 --- a/src/current/v24.2/cluster-setup-troubleshooting.md +++ b/src/current/v24.2/cluster-setup-troubleshooting.md @@ -232,9 +232,9 @@ If the DB Console then you might have a network partition. -**Explanation:** A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. +**Explanation:** -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} **Solution:** diff --git a/src/current/v24.2/ui-network-latency-page.md b/src/current/v24.2/ui-network-latency-page.md index c3a3c63f1a6..479052ad6c9 100644 --- a/src/current/v24.2/ui-network-latency-page.md +++ b/src/current/v24.2/ui-network-latency-page.md @@ -57,9 +57,7 @@ Hover over a cell to display more details: This specific information can help you understand the root cause of the connectivity issue. {{site.data.alerts.callout_info}} -A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. - -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} {{site.data.alerts.end}} ### Node liveness status diff --git a/src/current/v24.3/cluster-setup-troubleshooting.md b/src/current/v24.3/cluster-setup-troubleshooting.md index 1319c80d142..ec659cc2bcf 100644 --- a/src/current/v24.3/cluster-setup-troubleshooting.md +++ b/src/current/v24.3/cluster-setup-troubleshooting.md @@ -232,9 +232,9 @@ If the DB Console then you might have a network partition. -**Explanation:** A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. +**Explanation:** -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} **Solution:** diff --git a/src/current/v24.3/ui-network-latency-page.md b/src/current/v24.3/ui-network-latency-page.md index c3a3c63f1a6..479052ad6c9 100644 --- a/src/current/v24.3/ui-network-latency-page.md +++ b/src/current/v24.3/ui-network-latency-page.md @@ -57,9 +57,7 @@ Hover over a cell to display more details: This specific information can help you understand the root cause of the connectivity issue. {{site.data.alerts.callout_info}} -A network partition occurs when two or more nodes are prevented from communicating with each other in one or both directions. A network partition can be caused by a network outage or a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is disrupted in both directions. In an asymmetric partition, nodes can communicate in one direction but not the other. - -The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities]({% link {{ page.version.version }}/cockroach-start.md %}#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability. +{% include common/network-partitions.md %} {{site.data.alerts.end}} ### Node liveness status