auto-docs: Update property docs for tag v25.3.8 (#1587)

Co-authored-by: Paulo Borges <paulohtb6@gmail.com>

Author: vbotbuildovich

antora.yml

@@ -17,8 +17,8 @@ asciidoc:
     # Fallback versions
     # We try to fetch the latest versions from GitHub at build time
     # --
-    full-version: 25.3.7
-    latest-redpanda-tag: 'v25.3.7'
+    full-version: 25.3.8
+    latest-redpanda-tag: 'v25.3.8'
     latest-console-tag: 'v3.3.1'
     latest-release-commit: '6aa5af28b020b66e5caa966094882b7260497a53'
     latest-operator-version: 'v2.3.8-24.3.6'

docs-data/property-overrides.json

@@ -774,7 +774,7 @@
       "related_topics": [
         "xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]"
       ],
-      "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.",
+      "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.\n\nNOTE: Enabling this property will trigger decompression of message batches for topics on which validation is configured, which may lead to a modest increase in CPU load. Redpanda recommends monitoring CPU utilization after topics are configured.",
       "config_scope": "cluster"
     },
     "enable_shadow_linking": {
@@ -829,7 +829,7 @@
       "config_scope": "cluster"
     },
     "iceberg_default_catalog_namespace": {
-      "description": "The default namespace (database name) for Iceberg tables. All tables created by Redpanda will be placed in this namespace within the Iceberg catalog. Supports nested namespaces as an array of strings.\n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
+      "description": "The default Iceberg catalog namespace where Redpanda creates tables. Supports nested namespaces as an array of strings.\n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
       "version": "v25.3.5"
     },
     "iceberg_default_partition_spec": {
@@ -1132,6 +1132,7 @@
       "config_scope": "cluster"
     },
     "kafka_fetch_request_timeout_ms": {
+      "description": "Target duration for a single fetch request. The broker tries to complete each fetch within this duration, even if fewer bytes are available than requested.",
       "version": "v25.3.7"
     },
     "kafka_max_message_size_upper_limit_bytes": {
@@ -1215,6 +1216,10 @@
       "description": "Prevents log compaction from removing transaction metadata. Only set this to `true` if you experience stability issues related to transaction cleanup during compaction.",
       "config_scope": "cluster"
     },
+    "log_compaction_max_priority_wait_ms": {
+      "description": "Maximum time a priority partition (for example, `__consumer_offsets`) can wait for compaction before preempting regular compaction.",
+      "version": "v25.3.8"
+    },
     "log_compaction_merge_max_ranges": {
       "description": "The maximum range of segments that can be processed in a single round of adjacent segment compaction. If `null` (the default value), no maximum is imposed on the number of ranges that can be processed at once. A value below 1 effectively disables adjacent merge compaction.",
       "config_scope": "cluster"

…property-changes-v25.3.5-to-v25.3.7.json …property-changes-v25.3.7-to-v25.3.8.jsondocs-data/redpanda-property-changes-v25.3.5-to-v25.3.7.json renamed to docs-data/redpanda-property-changes-v25.3.7-to-v25.3.8.json docs-data/redpanda-property-changes-v25.3.5-to-v25.3.7.json renamed to docs-data/redpanda-property-changes-v25.3.7-to-v25.3.8.json

@@ -1,8 +1,8 @@
 {
   "comparison": {
-    "oldVersion": "v25.3.5",
-    "newVersion": "v25.3.7",
-    "timestamp": "2026-02-07T17:24:45.753Z"
+    "oldVersion": "v25.3.7",
+    "newVersion": "v25.3.8",
+    "timestamp": "2026-02-25T19:46:45.991Z"
   },
   "summary": {
     "newProperties": 1,
@@ -16,10 +16,10 @@
   "details": {
     "newProperties": [
       {
-        "name": "kafka_fetch_request_timeout_ms",
+        "name": "log_compaction_max_priority_wait_ms",
         "type": "integer",
-        "default": 5000,
-        "description": "Broker-side target for the duration of a single fetch request. The broker will try to complete fetches within the specified duration, even if it means returning less bytes in the fetch than are available."
+        "default": 3600000,
+        "description": "Maximum time a priority partition (for example, __consumer_offsets) can wait for compaction before preempting regular compaction."
       }
     ],
     "changedDefaults": [],

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

@@ -134,6 +134,7 @@ Redpanda 25.3 introduces the following configuration properties:
 * xref:reference:properties/cluster-properties.adoc#fetch_max_read_concurrency[`fetch_max_read_concurrency`]: Maximum concurrent partition reads per fetch request
 * xref:reference:properties/cluster-properties.adoc#kafka_max_message_size_upper_limit_bytes[`kafka_max_message_size_upper_limit_bytes`]: Maximum allowed `max.message.size` topic property value
 * xref:reference:properties/cluster-properties.adoc#kafka_produce_batch_validation[`kafka_produce_batch_validation`]: Validation level for produced batches
+* xref:reference:properties/cluster-properties.adoc#log_compaction_max_priority_wait_ms[`log_compaction_max_priority_wait_ms`]: Maximum time a priority partition can wait for compaction before preempting regular compaction
 * xref:reference:properties/cluster-properties.adoc#log_compaction_tx_batch_removal_enabled[`log_compaction_tx_batch_removal_enabled`]: Enable transactional batch removal during compaction
 * xref:reference:properties/cluster-properties.adoc#sasl_mechanisms_overrides[`sasl_mechanisms_overrides`]: SASL authentication mechanisms per listener
 

…chments/redpanda-properties-v25.3.7.json …chments/redpanda-properties-v25.3.8.jsonmodules/reference/attachments/redpanda-properties-v25.3.7.json renamed to modules/reference/attachments/redpanda-properties-v25.3.8.json modules/reference/attachments/redpanda-properties-v25.3.7.json renamed to modules/reference/attachments/redpanda-properties-v25.3.8.json

@@ -5583,7 +5583,7 @@
             "config_scope": "cluster",
             "default": "none",
             "defined_in": "src/v/config/configuration.cc",
-            "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.",
+            "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.\n\nNOTE: Enabling this property will trigger decompression of message batches for topics on which validation is configured, which may lead to a modest increase in CPU load. Redpanda recommends monitoring CPU utilization after topics are configured.",
             "enterprise_constructor": "restricted_only",
             "enterprise_restricted_value": [
                 "compat",
@@ -6333,7 +6333,7 @@
                 "redpanda"
             ],
             "defined_in": "src/v/config/configuration.cc",
-            "description": "The default Iceberg catalog namespace where Redpanda creates tables. Supports nested namespaces as an array of strings. \n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
+            "description": "The default Iceberg catalog namespace where Redpanda creates tables. Supports nested namespaces as an array of strings.\n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
             "is_deprecated": false,
             "is_enterprise": false,
             "items": {
@@ -7518,7 +7518,7 @@
             "default": 5000,
             "default_human_readable": "5 seconds",
             "defined_in": "src/v/config/configuration.cc",
-            "description": "Broker-side target for the duration of a single fetch request. The broker will try to complete fetches within the specified duration, even if it means returning less bytes in the fetch than are available.",
+            "description": "Target duration for a single fetch request. The broker tries to complete each fetch within this duration, even if fewer bytes are available than requested.",
             "is_deprecated": false,
             "is_enterprise": false,
             "maximum": 17592186044415,
@@ -7527,8 +7527,8 @@
             "needs_restart": false,
             "nullable": false,
             "type": "integer",
-            "visibility": "tunable",
-            "version": "v25.3.7"
+            "version": "v25.3.7",
+            "visibility": "tunable"
         },
         "kafka_group_recovery_timeout_ms": {
             "c_type": "std::chrono::milliseconds",
@@ -8581,6 +8581,27 @@
             "type": "integer",
             "visibility": "user"
         },
+        "log_compaction_max_priority_wait_ms": {
+            "c_type": "std::chrono::milliseconds",
+            "cloud_byoc_only": false,
+            "cloud_editable": false,
+            "cloud_readonly": false,
+            "cloud_supported": false,
+            "config_scope": "cluster",
+            "default": 3600000,
+            "default_human_readable": "1 hour",
+            "defined_in": "src/v/config/configuration.cc",
+            "description": "Maximum time a priority partition (for example, `__consumer_offsets`) can wait for compaction before preempting regular compaction.",
+            "is_deprecated": false,
+            "is_enterprise": false,
+            "maximum": 17592186044415,
+            "minimum": -17592186044416,
+            "name": "log_compaction_max_priority_wait_ms",
+            "needs_restart": false,
+            "nullable": false,
+            "type": "integer",
+            "visibility": "tunable"
+        },
         "log_compaction_merge_max_ranges": {
             "c_type": "uint32_t",
             "cloud_byoc_only": false,

modules/reference/partials/properties/cluster-properties.adoc

@@ -5016,14 +5016,14 @@ endif::[]
 
 Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.
 
-NOTE: Enabling this property will trigger decompression of message batches for topics on which validation is configured, which may lead to a modest increase in CPU load. Redpanda recommends monitoring CPU utilization after topics are configured.
-
 Values:
 
 * `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.
 * `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.
 * `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.
 
+NOTE: Enabling this property will trigger decompression of message batches for topics on which validation is configured, which may lead to a modest increase in CPU load. Redpanda recommends monitoring CPU utilization after topics are configured.
+
 ifndef::env-cloud[]
 .Enterprise license required
 [NOTE]
@@ -11382,6 +11382,53 @@ endif::[]
 |===
 
 
+=== log_compaction_max_priority_wait_ms
+
+Maximum time a priority partition (for example, `__consumer_offsets`) can wait for compaction before preempting regular compaction.
+
+[cols="1s,2a"]
+|===
+| Property | Value
+
+| Type
+| `integer`
+
+
+
+| Range
+| [`-17592186044416`, `17592186044415`]
+
+| Default
+|
+ifdef::env-cloud[]
+Available in the Redpanda Cloud Console
+endif::[]
+ifndef::env-cloud[]
+`3600000` (1 hour)
+endif::[]
+
+| Nullable
+| No
+
+| Unit
+| Milliseconds
+
+| Requires restart
+| No
+
+ifndef::env-cloud[]
+| Restored on xref:manage:whole-cluster-restore.adoc[Whole Cluster Restore]
+| Yes
+endif::[]
+
+ifndef::env-cloud[]
+| Visibility
+| Tunable
+endif::[]
+
+|===
+
+
 === log_compaction_merge_max_ranges
 
 The maximum range of segments that can be processed in a single round of adjacent segment compaction. If `null` (the default value), no maximum is imposed on the number of ranges that can be processed at once. A value below 1 effectively disables adjacent merge compaction.