v26.2.2

Features

• rpk sql debug bundle collects a diagnostic bundle from an Oxla (SQL) cluster. by @Bixkog in #31078 by @tyson-redpanda in #31294
• rpk generate grafana-dashboard gains a new operations-stretch dashboard: a Grafana dashboard for stretch clusters managed by the Redpanda Operator, covering cross-cluster raft health, StretchCluster member status, and operator reconcile health. Generate it with rpk generate grafana-dashboard --dashboard operations-stretch. by @RafalKorepta in #31641
• rpk generate grafana-dashboard now offers a load-factor dashboard showing utilization relative to capacity for key broker resources (CPU, IO scheduler, disk IOPS, memory, network bandwidth, client connections). by @travisdowns in #31555
• rpk now supports Shadow Link role sync in Redpanda Cloud clusters by @r-vasquez in #31625
• rpk shadow update now accepts a --config-file flag to apply a configuration file directly. by @r-vasquez in #31329

Bug Fixes

• Fix the registered config name for leader_balancer_node_mute_timeout. by @WillemKauf in #31359
• Fixed Schema Registry aborting the broker when a request failed before
  its deferred authorization check with
  schema_registry_enable_authorization enabled. Such requests now
  return an error response. by @nguyen-andrew in #31590
• Fixed a crash that could occur when removing a partition with a very large number of log segments, e.g. during partition rebalancing. by @pgellert in #31503
• Fixed a crash where a snapshot write failing on a full disk (ENOSPC) aborted
  the node with a misleading "snapshot writer has to be closed" assertion
  instead of surfacing the I/O error. by @nvartolomei in #31277
• Fixed a crash where a snapshot write failing on a full disk (ENOSPC) aborted the node with a misleading "snapshot writer has to be closed" assertion instead of surfacing the I/O error. by @nvartolomei in #31180 by @tyson-redpanda in #31294
• Fixed a race in the internal Kafka client where a concurrent request on a
  freshly established SASL connection could be sent before authentication
  finished, causing the broker to drop the connection. by @nvartolomei in #31273
• Fixed a race in the internal Kafka client where a concurrent request on a freshly established SASL connection could be sent before authentication finished, causing the broker to drop the connection. by @nvartolomei in #31152 by @tyson-redpanda in #31294
• Fixes a bug in timequeries on cloud topics which could result in returning an offset up to one indexing interval (4_MiB of records by default) later than the first record at or after the requested timestamp by @WillemKauf in #31417
• Fixes a bug in which L0 batches in a cloud topic forgot to preserve last_offset_delta in their header, leading to an under-declared last offset which can stall consumers, skip records, or halt exact-offset replication. by @WillemKauf in #31364
• Fixes a bug in which timequeries on a cloud topic could either fail by dropping the client connection or by returning an unfetchable offset below a partition's start offset. by @WillemKauf in #31424
• Fixes a bug in which topics with min.compaction.lag.ms left unconfigured with produced batches holding timestamps in the future would be considered ineligible for compaction by @WillemKauf in #31458
• Fixes a bug in which transient TOPIC_AUTHORIZATION_FAILED errors and SASL authentication failures were possible during application of a controller snapshot. by @WillemKauf in #31435
• Fixes a bug where corrupted storage would not yield a bad CRC in returned record batches. by @andrwng in #31389
• Fixes a bug where having a cloud topic read replica on a given cluster would prevent L0 objects on that cluster from being garbage collected. by @andrwng in #31390
• Fixes a potential crash in `DescribeLogDirs` by @WillemKauf in #31173 by @tyson-redpanda in #31294
• Fixes an issue where backpressure from the Iceberg coordinator would cause high CPU load on the translators. by @andrwng in #31583
• Fixes potential unbounded growth of various s3_fifo users under specific workloads. by @ballard26 in #31643
• HTTP Proxy: Consumer group fetches no longer fail indefinitely with `offset_out_of_range` after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset (`auto.offset.reset=earliest`). by @bartoszpiekny-redpanda in #31064 by @tyson-redpanda in #31294
• Lifecycle fix on groups by @joe-redpanda in #31171 by @tyson-redpanda in #31294
• Redpanda will no longer incorrectly accept client-produced control batches. by @andrwng in #31605
• Updating a Shadow Link that uses PLAIN authentication no longer fails when the password is omitted; the stored password is preserved. by @r-vasquez in #31394
• #31446 rpk connect install --connect-version no longer rejects versions with a
  segment of three or more digits, which had blocked pinning any Redpanda Connect
  release since 4.100.0. Malformed versions with trailing characters are now
  rejected during validation rather than failing at download. by @prakhargarg105 in #31447
• #31548 rpk connect upgrade no longer fails to determine the currently-installed Redpanda Connect version when that version has a segment of three or more digits, which had blocked upgrading any Connect install since 4.100.0. by @JakeSCahill in #31549
• rpk security secrets list no longer truncates its output at 100 secrets. by @simon0191 in #31434
• rpk shadow create no longer fails secret-reference validation on clusters
  with more than one page of REDPANDA_CLUSTER-scoped secrets. by @simon0191 in #31434
• rpk shadow update in editor mode now replaces the entire Shadow Link configuration instead of merging changed fields, so list-valued fields (e.g. topic filters) can shrink or be cleared. by @r-vasquez in #31394
• The describe-storage RPK command will now have a valid output for tiered_v2 topics by @andrwng in #31267
• Avoids a reactor stall on the Iceberg coordinator snapshotting mechanism when there is a large number of parquet files pending commit by @nvartolomei in #31278
• Fixes a rare crash in Cloud Topics caused by replication failures. by @Lazin in #31523
• Fixed a use-after-free during shutdown in the Kafka quota manager's garbage collection. by @nvartolomei

Improvements

• Cloud Topics compaction will now commit work in chunks, which should result in more stable compaction for partitions with a large amount of data. by @WillemKauf in #31312
• Added a `schema_registry_replay_on_startup` cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request. by @sjust-redpanda in #31137 by @tyson-redpanda in #31294
• Avoid oversized allocations for some of the `schema_registry` and `pandaproxy` handler interfaces. by @WillemKauf in #31103 by @tyson-redpanda in #31294
• Fixes an issue where /v1/usage responses could cause oversized allocations for clusters with a large number of Iceberg-enabled topics. by @WillemKauf in #31333
• HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset. by @bartoszpiekny-redpanda in [#31112](https://github.com/redpanda-dat...

v26.1.17

Bug Fixes

• Fixed an issue where audit-log initialization unconditionally sent a CreateTopics request to the controller leader, causing authentication and the admin API to be rejected cluster-wide (with audit_failure_policy=reject) for the duration of any prolonged leaderless state. Initialization now checks the local topic table first and skips the CreateTopics call when the audit topic already exists. by @andresaristizabal-rp in #31411
• Fixed an issue where backpressure from the Iceberg coordinator caused high CPU load on the Datalake translators. The translation loop was treating a backpressured fetch as a successful iteration and cancelling its retry jitter, causing it to spin as fast as the RPC completed rather than applying the normal jittered sleep. by @pgellert in #31419
• Reverted the c-ares DNS resolver from 1.34.7 back to 1.34.6. c-ares 1.34.7 contains an upstream regression (c-ares/c-ares#1256) where a DNS query completion callback can silently never be invoked, which could leave an internal broker-to-broker RPC connection permanently unable to reconnect after a peer broker restart. Affected clusters showed persistently under-replicated partitions and failing broker readiness probes. Reverting c-ares reintroduces CVE-2026-33630; the CVE fix will be re-applied once upstream resolves the regression. by @bartoszpiekny-redpanda in #31634

Full Changelog: v26.1.16...v26.1.17

v25.3.17

Features

• adds the cloud_storage_prefetch_segments_max cluster config which can be used to enable small segment prefetching in cloud storage. by @ballard26 in #29795

Bug Fixes

• Reverted the c-ares DNS resolver from 1.34.7 back to 1.34.6. c-ares 1.34.7 contains an upstream regression (c-ares/c-ares#1256) where a DNS query's completion callback can silently never be invoked, which could leave an internal broker-to-broker RPC connection permanently unable to reconnect after a peer broker restart. Affected clusters showed persistently under-replicated partitions and failing broker readiness probes, even though the remaining replicas kept a healthy quorum and continued serving traffic. Reverting c-ares reintroduces CVE-2026-33630. The CVE fix will be re-applied once an upstream c-ares release fixes the regression. by @pgellert in #31637
• Fixed a memory over-allocation in the Kafka fetch path where a partition with an inflated max.message.bytes (e.g. UINT32_MAX) could monopolize the entire shard's fetch memory budget, starving other partitions and causing fetch timeouts or broker OOM. by @ballard26 in #30314
• Fixed an audit initialization deadlock where the audit subsystem would retry indefinitely waiting for a controller leader, permanently wedging startup on clusters without an elected leader. Audit initialization now reads the local topic table directly and marks the subsystem misconfigured rather than silently dropping records. by @bartoszpiekny-redpanda in #31587
• #31552 rpk connect upgrade no longer fails to determine the currently-installed Redpanda Connect version when that version has a segment of three or more digits, which had blocked upgrading any Connect install since 4.100.0. by @JakeSCahill in #31553

Full Changelog: v25.3.16...v25.3.17

v26.1.16

IMPORTANT: Do not install the 26.1.16 release. A critical bug was identified that has broad implications that can create instability for long-running clusters. This issue is fixed in 26.1.17. Please upgrade directly to 26.1.17 or 26.2.x

Bug Fixes

• Fixed a crash that could occur when removing a partition with a very large number of log segments, e.g. during partition rebalancing. by @pgellert in #31505
• Fixed a crash where a snapshot write failing on a full disk (ENOSPC) aborted the node with a misleading "snapshot writer has to be closed" assertion instead of surfacing the I/O error. by @nvartolomei in #31186
• Fixed a double-free / use-after-free in c-ares query-completion handling (CVE-2026-33630). by @bartoszpiekny-redpanda in #31486
• Fixed a race in the internal Kafka client where a concurrent request on a freshly established SASL connection could be sent before authentication finished, causing the broker to drop the connection. by @nvartolomei in #31192
• #31550 rpk connect upgrade no longer fails to determine the currently-installed Redpanda Connect version when that version has a segment of three or more digits, which had blocked upgrading any Connect install since 4.100.0. by @JakeSCahill in #31551

Full Changelog: v26.1.15...v26.1.16

v25.3.16

IMPORTANT: Do not install the 25.13.16 release. A critical bug was identified that has broad implications that can create instability for long-running clusters. This issue is fixed in 25.3.17. Please upgrade directly to 25.3.17, 26.1.17, or 26.2.x

Bug Fixes

• Changes to cloud_storage_throughput_limit_percent cluster config now take effect at runtime instead of being ignored until restart. by @nvartolomei in #30232
• Fix consumer group lag metrics inflated after retention or trim-prefix. by @bartoszpiekny-redpanda in #30902
• Fix consumer group lag metrics reporting 0 for read-replica topics. by @bartoszpiekny-redpanda in #30950
• Fixed a crash that could occur when removing a partition with a very large number of log segments, e.g. during partition rebalancing. by @pgellert in #31504
• Fixed a crash where a snapshot write failing on a full disk (ENOSPC) aborted the node with a misleading "snapshot writer has to be closed" assertion instead of surfacing the I/O error. by @nvartolomei in #31188
• Fixed a double-free / use-after-free in c-ares query-completion handling (CVE-2026-33630). by @bartoszpiekny-redpanda in #31485
• Fixed a leak in the Iceberg translation subsystem where per-partition metrics were not released after a partition was removed from a broker. by @nvartolomei in #30705
• Fixed a race in the internal Kafka client where a concurrent request on a freshly established SASL connection could be sent before authentication finished, causing the broker to drop the connection. by @nvartolomei in #31191
• Fixes a bug in OffsetForLeaderEpoch handling with tiered topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage. by @WillemKauf in #31075
• Fixes a bug in which a generate_report() request to the transform system could result in a nullptr dereference at startup. by @WillemKauf in #30911
• Fixes a bug in which hung requests to the schema registry or in shadow linking could cause a deadlock during shutdown. by @WillemKauf in #30789
• Fixes a reactor stall seen when there are a large number of pending files in the Iceberg Topics coordinator. by @andrwng in #30881
• Fixes a wedge in multi-output transforms where a produce failure on one output topic silently stalled the processor instead of restarting it. by @WillemKauf in #30856
• HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset (auto.offset.reset=earliest). by @bartoszpiekny-redpanda in #31208
• Lifecycle fix on groups. by @joe-redpanda in #31183
• Upgrade krb5 to 1.22.2 to address CVE-2026-40355 and CVE-2026-40356 (NegoEx parsing vulnerabilities). by @tyson-redpanda in #30875
• Upgraded Go toolchain to 1.26.5 to address CVE-2026-39822 (os.Root symlink escape). by @bartoszpiekny-redpanda in #31487
• Upgraded OpenSSL from 3.0.20 to 3.0.21 to resolve CVEs fixed in the 3.0.21 release (2026-06-09). by @tyson-redpanda in #30812
• Fixed a rare condition where Tiered Storage metadata spillover could get permanently stuck on partitions with small, frequent segments, repeatedly logging "Can't apply spillover_cmd" and leaving orphaned spillover manifest objects in the bucket. by @Lazin in #31464
• Fixed an allocation double-free triggered by no-op replication-factor changes. by @joe-redpanda in #31194
• Fixes a bug in which internal topics could be auto-created with the wrong topic properties. by @WillemKauf in #31241
• Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts. by @stevenpall in #31255
• Broker-internal authorisation probes (metadata visibility filtering, init_producer_id write fall back, OffsetForLeaderEpoch cluster_action fast path) no longer emit denied-access audit events attributed to the client. by @JFlath in #31325
• OffsetForLeaderEpoch no longer logs a spurious authz failure for non-superuser consumers. by @JFlath in #31325
• rpk connect install --connect-version no longer rejects versions with a segment of three or more digits, which had blocked pinning any Redpanda Connect release since 4.100.0. by @prakhargarg105 in #31451

Improvements

• Avoid oversized allocations for some of the schema_registry and pandaproxy handler interfaces. by @WillemKauf in #31201
• HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset. by @bartoszpiekny-redpanda in #31224
• Iceberg Topics will stop creating new parquet files if there is a large backlog of files not yet committed to the Iceberg catalog. This helps avoid an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31037
• Improves false positive detection in the cloud storage scrubber to filter out compacted reuploads. by @oleiman in #30121
• Make the fetch path more resilient to errors in single partitions. by @WillemKauf in #30112
• Prevent oversized allocations in the kafka layer when utilizing large consumer groups. by @WillemKauf in #30752
• Purging an Iceberg table managed by the filesystem catalog will now delete all the table's files, not just the metadata files. by @wdberkeley in #30700
• The Iceberg Topics Coordinator will now commit to the Iceberg catalog in chunks, avoiding an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31037
• rpk cluster health will now display any nodes that may be in maintenance mode. by @alextreichler in #31351
• Adds stuck raft0 escape hatches. by @joe-redpanda in #31198
• Decommission may now cancel a stalled cluster node add. by @joe-redpanda in #30661

Full Changelog: v25.3.15...v25.3.16

v26.1.15

Bug Fixes

• Fix the registered config name for leader_balancer_node_mute_timeout. by @WillemKauf in #31360
• Fixes a bug in which L0 batches in a cloud topic forgot to preserve last_offset_delta in their header, leading to an under-declared last offset which can stall consumers, skip records, or halt exact-offset replication. by @WillemKauf in #31363
• Fixes a bug in which topics with min.compaction.lag.ms left unconfigured with produced batches holding timestamps in the future would be considered ineligible for compaction by @WillemKauf in #31459
• Fixes a bug in which transient TOPIC_AUTHORIZATION_FAILED errors and SASL authentication failures were possible during application of a controller snapshot. by @WillemKauf in #31437
• Fixes a bug where corrupted storage would not yield a bad CRC in returned record batches. by @andrwng in #31388
• Fixes a bug where having a cloud topic read replica on a given cluster would prevent L0 objects on that cluster from being garbage collected. by @andrwng in #31391
• Updating a Shadow Link that uses PLAIN authentication no longer fails when the password is omitted; the stored password is preserved. by @r-vasquez in #31421
• #31448 rpk connect install --connect-version no longer rejects versions with a
  segment of three or more digits, which had blocked pinning any Redpanda Connect
  release since 4.100.0. Malformed versions with trailing characters are now
  rejected during validation rather than failing at download. by @prakhargarg105 in #31449
• rpk security secrets list no longer truncates its output at 100 secrets. by @simon0191 in #31436
• rpk shadow create no longer fails secret-reference validation on clusters
  with more than one page of REDPANDA_CLUSTER-scoped secrets. by @simon0191 in #31436
• rpk shadow update in editor mode now replaces the entire Shadow Link configuration instead of merging changed fields, so list-valued fields (e.g. topic filters) can shrink or be cleared. by @r-vasquez in #31421

Improvements

• #31335 Fixes an issue where /v1/usage responses could cause oversized allocations for clusters with a large number of Iceberg-enabled topics. by @WillemKauf in #31337
• rpk cluster health will now display any nodes that may be in maintenance mode. by @alextreichler in #31352

Full Changelog: v26.1.14...v26.1.15

v26.2.1

Redpanda v26.2 Release Notes

Features

• Redpanda Enterprise (excludes Redpanda BYOC/Dedicated/Serverless) now supports major version rollback via ‘unfinalized’ upgrades. rpk cluster upgrade finalize and rpk cluster upgrade status manage deferred (unfinalized) major-version upgrades. (#30930)
• Shadowing from non-Redpanda Schema Registries using the HTTP Schema Registry API. rpk shadow provides support for the new Schema Registry Sync option shadow_schema_registry_api in Shadow Links. (#30860)
• Schema Registry sync shadow links now enforce the link's max_source_requests_per_second setting (default 30 requests/sec) when reading from the source registry, and honor a throttling source's Retry-After response header. (#31101)
• Schema Registry shadowing now exports its sync totals as shadow_link_schema_registry_* counters on the internal and public metrics endpoints, labelled by shadow_link_name. (#31067)
• Shadow links can now mirror RBAC roles from the source cluster to the destination. Configure role sync on the link with a sync interval and role-name filters to select which roles are kept in sync. (#30946)
• rpk now supports role_sync_options when creating a Shadow Link. (#30909)
• Shadowing now supports Cloud Topics. (#30073)
• Tiered Storage V2 beta. A new default_redpanda_storage_mode_tiered_impl cluster config (tiered_v1 | tiered_v2, default tiered_v1) selects whether the tiered value of the redpanda.storage.mode topic property refers to classic Tiered Storage or the new version of tiered storage. Tiered Storage v2 is a beta feature in v26.2. (#30966)
• New read-only redpanda.storage.mode.impl topic property reports the exact implementation of every topic's storage mode (unset|local|tiered_v1|tiered_v2|cloud), and can be supplied on topic creation to select the storage mode precisely. Topics using the tiered_v2 implementation (beta) can only be created once the whole cluster runs v26.2. (#30966)
• Schema Registry context support is now enabled by default. Subjects of the form :.context:subject are parsed into a separate context. See the upgrade considerations before upgrading clusters that may have stored literal :.-prefixed subject names. (#30365)
• Schema Registry now accepts /contexts/{context}/... prefixed URLs on all endpoints, allowing serde clients to target a non-default context by configuring their base URL (e.g. schema.registry.url=http://host:8081/contexts/.myctx). (#30189)
• Add OAUTHBEARER SASL mechanism support to rpk, enabling OIDC-based authentication for the Kafka client, admin API, and schema registry. Pass the token via --password (raw value or token:<TOKEN> format) with --sasl-mechanism OAUTHBEARER. (#30169)
• #30222 Add OAUTHBEARER SASL mechanism support to the admin API endpoint used by rpk debug remote-bundle start, enabling remote debug bundle collection against clusters configured with OAUTHBEARER authentication. (#30225)
• rpk debug remote-bundle start now supports OAUTHBEARER (OIDC) profiles. Pass the bearer token via --password (or kafka_api.sasl.password in the rpk profile) when sasl.mechanism is OAUTHBEARER. (#30277)
• Adds a new layout key to the Iceberg translation mode as a config string, in the value section. layout supports nested and flat; flat is the default and matches previous behavior. (#30917)
• Iceberg translation now supports schema registry contexts. Configure a topic to resolve schemas in a context via the redpanda.schema.registry.context topic property. (#30132)
• Added per-entity Kafka quota metrics. Set kafka_per_entity_quota_metrics to true (default false, no restart) to expose per-entity throttling and throughput counters for produce, fetch, and partition-mutation quotas. (#30832)
• Add rpk check as a new managed plugin for production readiness validation. It checks cluster health, broker configuration, security settings, replication factors, licensing, TLS, and Kubernetes resource configuration against the official production readiness checklists. Supports auto-install, upgrade, and uninstall via rpk check install, rpk check upgrade, and rpk check uninstall. (#30146)
• Add rpk k8s, a new managed plugin for interacting with Redpanda clusters running on Kubernetes. On first use, rpk auto-downloads, checksum-verifies, and caches the plugin; manage it explicitly with rpk k8s install / upgrade / uninstall. (#30833)
• Added an admin API endpoint to cancel an in-progress controller (raft0) reconfiguration. (#30918)
• Added redpanda_cluster_health_* Prometheus metrics (public and internal endpoints) exposing the same inputs as rpk cluster health, including nodes_down, leaderless_partitions, under_replicated_partitions, unhealthy_reasons, and a metadata_age_seconds freshness gauge. Disabled by default; enable with the new health_monitor_metrics_enabled cluster property. (#30769)
• Expose estimated cloud instance hardware capacity (vCPUs, memory, disk, network bandwidth, and IOPS) as Prometheus metrics, derived from the detected cloud instance type. (#30742)
• rpk --print-tree emits the full rpk command tree as a single JSON document, suited for LLMs and automation. (#30380)
• rpk redpanda admin broker list now includes a --detailed flag with additional per-path disk usage information, and supports the --format json/yaml flag. (#30096)
• Added rpk cloud auth token to print the current cloud auth token. (#29964)
• New metric vectorized_kafka_leadership_changes counts leadership changes in a topic. (#30117)
• New cluster config oidc_http_proxy_url routes OIDC discovery and JWKS fetches through an HTTP forward proxy. Set to a URL of the form http://host:port or https://host:port to enable; leave unset (the default) to connect to the OIDC endpoint directly. Live-reloadable, no broker restart required. (#30268)
• New cluster configs oidc_http_proxy_username / oidc_http_proxy_password add HTTP Basic authentication to the OIDC forward proxy; (#30738)
• New configuration iceberg_rest_catalog_credentials_host: the hostname to connect to for retrieving role-based credentials for the Iceberg REST catalog, for cases where the REST catalog uses a different credentials source than cloud storage. (#30284)

Improvements

• max_concurrent_producer_ids and max_transactions_per_coordinator now default to 100,000 and 10,000 respectively (previously unlimited), reducing memory usage from accumulated producer state. Existing explicit overrides are unaffected. (#30058)
• Prevent oversized allocations/OOMs when using a large number of ACLs in Redpanda. (#30967)
• Prevent oversized allocations in the Kafka layer when using large consumer groups. (#30744)
• The schema_registry_cache_schema_count metric now includes a type label (AVRO, JSON, PROTOBUF), replacing the single per-context gauge with one gauge per schema type per context. Dashboards or alerts that query this metric without filtering on type should be updated to sum across the label, e.g. sum by (context) (redpanda_schema_registry_cache_schema_count). (#30725)
• Avoid potential oversized allocations in the segment index materialization path. (#30236)
• Iceberg Topics will stop creating new Parquet files if there is a large backlog of files not yet committed to the Iceberg catalog, and the Iceberg Topics Coordinator now commits to the catalog in chunks — both changes help avoid an OOM when the catalog has rejected Redpanda commits for a prolonged period. (#30958)
• Fixed unnecessary memory allocations/deallocations on the L0 write path in Cloud Topics. (#30980)
• Avoid recompression o...

v26.1.14

Bug Fixes

• Fixed a cloud-topics epoch fencing race where an epoch bump whose replication failed could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition. by @Lazin in #31140
• Fixes a bug in OffsetForLeaderEpoch handling with tiered topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage. by @WillemKauf in #31074
• Fixes a potential crash in DescribeLogDirs by @WillemKauf in #31196
• HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset (auto.offset.reset=earliest). by @bartoszpiekny-redpanda in #31207
• Lifecycle fix on groups by @joe-redpanda in #31182
• #30885 Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts. by @stevenpall in #30886
• #31238 Fixes a bug in which internal topics could be auto-created with the wrong topic properties by @WillemKauf in #31239
• fix allocation double free on no-op rf changes by @joe-redpanda in #31116

Improvements

• Added a `schema_registry_replay_on_startup` cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request. by @sjust-redpanda in #31174
• Avoid oversized allocations for some of the `schema_registry` and `pandaproxy` handler interfaces. by @WillemKauf in #31200
• HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset. by @bartoszpiekny-redpanda in #31225
• Optimize the `schema_registry` recovery path by caching references when canonicalizing schemas by @WillemKauf in #31193
• Schema Registry now replays the internal `_schemas` topic exactly once when recovering on startup, instead of running redundant concurrent replays; cold start of a large registry is significantly faster. by @sjust-redpanda in #31174

Full Changelog: v26.1.13...v26.1.14

v26.1.13

Bug Fixes

• Fix consumer group lag metrics reporting 0 for read-replica topics. by @bartoszpiekny-redpanda in #30939
• Fixed a cluster membership lock that could occur when a node was decommissioned while it was being added as a controller (raft0) learner. by @mmaslankaprv in #31091
• Fixed a potential broker crash (use-after-free) in the cloud topics metastore when accessing Raft state during leadership changes. by @nvartolomei in #31052
• Fixes a bug in cloud topics compaction that could cause repeated no-op compactions if the topic uses retention or transactions. by @andrwng in #31124
• Fixes a bug where Cloud Topics with the compact cleanup policy would have log retention policies applied to them. by @andrwng in #31111
• Fixes an issue where cluster linking would not replicate the partition start offset. by @andrwng in #31000
• rpk ai no longer requires a selected Redpanda Cloud cluster to run. The AI CLI uses its own rpk ai auth login and rpk ai env use, independent of any rpk cloud session. by @birdayz in #31079
• fix a latent double get_exception call on a failed future in cloud topics metastore by @oleiman in #31045

Improvements

• Adds a new enable_development_metrics cluster configuration (false by default, runtime configurable). When enabled, internal_rpc_latency metrics are exposed to the internal /metrics endpoint. This family of metrics can be expensive (large number of series) - leave it set to false to save on metrics scraping costs. by @WillemKauf in #30957
• Fixes a bug where unnecessary memory allocations/deallocations were being made on the L0 write path in cloud topics by @WillemKauf in #30983
• Iceberg Topics will stop creating new parquet files if there is a large backlog of files not yet committed to the Iceberg catalog. This helps avoid an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31036
• Optimize the ACL authorization path for all callers (Kafka handlers, schema registry, Pandaproxy & Iceberg) by @WillemKauf in #30969
• Prevent oversized allocations/OOMs when using a large number of ACLs in redpanda by @WillemKauf in #30969
• The Iceberg Topics Coordinator will now commit to the Iceberg catalog in chunks, avoiding an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31036

Full Changelog: v26.1.12...v26.1.13

v26.1.12

Bug Fixes

• Fixes a bug in which a generate_report() request to the transform system could result in a nullptr dereference at startup by @WillemKauf in #30910
• Fixes a bug in which a stale read in the l0 write scheduler could result in a division by zero (raising SIGFPE). by @WillemKauf in #30920
• Fixes a reactor stall seen when there are a large number of pending files in the Iceberg Topics coordinator. by @andrwng in #30880
• PR #30929 [v26.1.x] datalake: Fix deleted namespace race for REST_HADOOP catalog by @wdberkeley
• PR #30944 [v26.1.x] dt/kgo: surface worker crashes as descriptive errors by @nvartolomei

Improvements

• adds stuck raft0 escape hatches by @vbotbuildovich in #30945
• PR #30922 [v26.1.x] [CORE-16282] json: make the schema walk keyword-aware by @mnajda-redpanda

Full Changelog: v26.1.11...v26.1.12