auto-docs: Update property docs for tag v26.1.4

antora.yml

@@ -17,8 +17,8 @@ asciidoc:
     # Fallback versions
     # We try to fetch the latest versions from GitHub at build time
     # --
-    full-version: 26.1.2
-    latest-redpanda-tag: 'v26.1.2'
+    full-version: 26.1.5
+    latest-redpanda-tag: 'v26.1.5'
     latest-console-tag: 'v3.3.1'
     latest-release-commit: '35a825c9c1880ebeedf4c18bb8c6cceaa63566c1'
     latest-operator-version: 'v2.3.8-24.3.6'

docs-data/property-overrides.json

@@ -1411,7 +1411,7 @@
       "config_scope": "cluster"
     },
     "max_concurrent_producer_ids": {
-      "description": "Maximum number of active producer sessions per shard. Each shard tracks producer IDs using an LRU (Least Recently Used) eviction policy. When the configured limit is exceeded, the least recently used producer IDs are evicted from the cache.\n\nIf you upgrade from 23.2.x to 23.3.x and encounter `OUT_OF_SEQUENCE` errors, consider increasing this value. In 23.3.x, the configuration changed from a per-partition basis to a per-shard basis.\n\nIMPORTANT: The default value is unlimited, which can lead to unbounded memory growth and out-of-memory (OOM) crashes in production environments with heavy producer usage, especially when using transactions or idempotent producers. Set a reasonable limit in production deployments.",
+      "description": "Maximum number of active producer sessions per shard. Each shard tracks producer IDs using an LRU (Least Recently Used) eviction policy. When the configured limit is exceeded, the least recently used producer IDs are evicted from the cache.\n\nIf you upgrade from 23.2.x to 23.3.x and encounter `OUT_OF_SEQUENCE` errors, consider increasing this value. In 23.3.x, the configuration changed from a per-partition basis to a per-shard basis.\n\nIMPORTANT: Set a value appropriate for your workload and memory budget, especially when using transactions or idempotent producers.",
       "related_topics": [
         "xref:develop:transactions.adoc#tune-producer-id-limits[Tune producer ID limits]",
         "xref:reference:properties/cluster-properties.adoc#transactional_id_expiration_ms[transactional_id_expiration_ms]",

docs-data/redpanda-property-changes-v26.1.2-to-v26.1.4.json

@@ -0,0 +1,47 @@
+{
+  "comparison": {
+    "oldVersion": "v26.1.2",
+    "newVersion": "v26.1.4",
+    "timestamp": "2026-04-11T15:34:55.805Z"
+  },
+  "summary": {
+    "newProperties": 0,
+    "changedDefaults": 2,
+    "changedDescriptions": 0,
+    "changedTypes": 0,
+    "deprecatedProperties": 0,
+    "removedDeprecatedProperties": 0,
+    "removedProperties": 0,
+    "emptyDescriptions": 2
+  },
+  "details": {
+    "newProperties": [],
+    "changedDefaults": [
+      {
+        "name": "max_concurrent_producer_ids",
+        "oldDefault": "Maximum value",
+        "newDefault": 100000
+      },
+      {
+        "name": "max_transactions_per_coordinator",
+        "oldDefault": "Maximum value",
+        "newDefault": 10000
+      }
+    ],
+    "changedDescriptions": [],
+    "changedTypes": [],
+    "deprecatedProperties": [],
+    "removedDeprecatedProperties": [],
+    "removedProperties": [],
+    "emptyDescriptions": [
+      {
+        "name": "redpanda.remote.allowgaps",
+        "type": "boolean"
+      },
+      {
+        "name": "redpanda.virtual.cluster.id",
+        "type": "string"
+      }
+    ]
+  }
+}

docs-data/redpanda-property-changes-v26.1.1-to-v26.1.2.json → docs-data/redpanda-property-changes-v26.1.4-to-v26.1.5.json

@@ -1,8 +1,8 @@
 {
   "comparison": {
-    "oldVersion": "v26.1.1",
-    "newVersion": "v26.1.2",
-    "timestamp": "2026-04-03T17:46:32.769Z"
+    "oldVersion": "v26.1.4",
+    "newVersion": "v26.1.5",
+    "timestamp": "2026-04-16T13:21:44.556Z"
   },
   "summary": {
     "newProperties": 0,

modules/get-started/pages/release-notes/redpanda.adoc

@@ -147,6 +147,12 @@ NOTE: Cloud Topics requires an Enterprise license. For more information, contact
 * xref:reference:properties/cluster-properties.adoc#log_compaction_tx_batch_removal_enabled[`log_compaction_tx_batch_removal_enabled`]: Changed from `false` to `true`.
 * xref:reference:properties/cluster-properties.adoc#tls_v1_2_cipher_suites[`tls_v1_2_cipher_suites`]: Changed from OpenSSL cipher names to IANA cipher names.
 
+==== v26.1.4
+
+* xref:reference:properties/cluster-properties.adoc#max_concurrent_producer_ids[`max_concurrent_producer_ids`]: Changed from unlimited to `100000` to prevent unbounded memory growth with heavy producer usage.
+
+* xref:reference:properties/cluster-properties.adoc#max_transactions_per_coordinator[`max_transactions_per_coordinator`]: Changed from unlimited to `10000` to prevent resource exhaustion from excessive transaction sessions.
+
 === Removed properties
 
 The following deprecated configuration properties have been removed in v26.1.1. If you have any of these in your configuration files, update them according to the guidance below.

modules/reference/attachments/redpanda-properties-v26.1.2.json → modules/reference/attachments/redpanda-properties-v26.1.4.json

@@ -8704,7 +8704,8 @@
             "description": "Mode of the leader balancer optimization strategy.\n\nAccepted values:\n\n* `calibrated` (default): An adaptive strategy that samples potential moves and prioritizes high-impact transfers. Minimizes unnecessary leader movement while achieving balance over time. Best for most production workloads.\n* `random`: Accepts the first random move that improves balance. Less efficient than `calibrated` because it doesn't prioritize high-impact moves. Available as a fallback if `calibrated` causes unexpected behavior.\n\nLegacy values `greedy_balanced_shards` and `random_hill_climbing` are treated as `calibrated`.",
             "enum": [
                 "calibrated",
-                "random"
+                "random",
+                "greedy"
             ],
             "example": "`model::leader_balancer_mode_to_string(         model::leader_balancer_mode::calibrated)`",
             "is_deprecated": false,
@@ -9430,9 +9431,9 @@
             "cloud_readonly": false,
             "cloud_supported": false,
             "config_scope": "cluster",
-            "default": "Maximum value",
+            "default": 100000,
             "defined_in": "src/v/config/configuration.cc",
-            "description": "Maximum number of active producer sessions per shard. Each shard tracks producer IDs using an LRU (Least Recently Used) eviction policy. When the configured limit is exceeded, the least recently used producer IDs are evicted from the cache.\n\nIf you upgrade from 23.2.x to 23.3.x and encounter `OUT_OF_SEQUENCE` errors, consider increasing this value. In 23.3.x, the configuration changed from a per-partition basis to a per-shard basis.\n\nIMPORTANT: The default value is unlimited, which can lead to unbounded memory growth and out-of-memory (OOM) crashes in production environments with heavy producer usage, especially when using transactions or idempotent producers. Set a reasonable limit in production deployments.",
+            "description": "Maximum number of active producer sessions per shard. Each shard tracks producer IDs using an LRU (Least Recently Used) eviction policy. When the configured limit is exceeded, the least recently used producer IDs are evicted from the cache.\n\nIf you upgrade from 23.2.x to 23.3.x and encounter `OUT_OF_SEQUENCE` errors, consider increasing this value. In 23.3.x, the configuration changed from a per-partition basis to a per-shard basis.\n\nIMPORTANT: Set a value appropriate for your workload and memory budget, especially when using transactions or idempotent producers.",
             "is_deprecated": false,
             "is_enterprise": false,
             "maximum": 18446744073709551615,
@@ -9512,7 +9513,7 @@
             "cloud_readonly": false,
             "cloud_supported": false,
             "config_scope": "cluster",
-            "default": "Maximum value",
+            "default": 10000,
             "defined_in": "src/v/config/configuration.cc",
             "description": "Specifies the maximum number of active transaction sessions per coordinator. When the threshold is passed Redpanda terminates old sessions. When an idle producer corresponding to the terminated session wakes up and produces, it leads to its batches being rejected with invalid producer epoch or invalid_producer_id_mapping error (depends on the transaction execution phase).\n\nFor details, see xref:develop:transactions#transaction-usage-tips[Transaction usage tips].",
             "is_deprecated": false,