This topic includes new content added in version {page-component-version} Beta. For a complete list of all product updates, see the Redpanda release notes. See also:
-
redpanda-cloud:get-started:whats-new-cloud.adoc
-
Redpanda Cloud vs Self-Managed feature compatibility
The Redpanda Admin API now includes new health probes to help you ensure safe broker restarts and upgrades. The pre_restart_probe
endpoint identifies potential risks if a broker is restarted, and post_restart_probe
indicates how much of its workloads a broker has reclaimed after the restart. See also:
-
manage:cluster-maintenance/rolling-restart.adoc
-
upgrade:rolling-upgrade.adoc
The Redpanda Console v3.0.0 beta release includes the following updates:
Redpanda Console now supports unified authentication and authorization between Console and Redpanda, including user impersonation. This means you can authenticate to Redpanda using the same credentials you use for Redpanda Console.
See console:config/security/authentication.adoc for more information.
upgrade:partial$console/v3-breaking-changes.adoc
Action required: upgrade:migrate/console-v3.adoc.
Iceberg-enabled topics now support custom partitioning for improved query performance, snapshot expiry, and a dead-letter queue for invalid records. Schema evolution is also supported with schema mutations implemented according to the Iceberg specification.
Redpanda now supports normalization of Protobuf schemas in the Schema Registry. You can normalize Avro, JSON, and Protobuf schemas both during registration and lookup. For more information, see the Schema Registry overview, and the Schema Registry API reference.
You now can configure Kafka clients to authenticate using SASL/PLAIN with a single account using the same username and password. Unlike SASL/SCRAM, which uses a challenge response with hashed credentials, SASL/PLAIN transmits plaintext passwords. You enable SASL/PLAIN by appending PLAIN
to the list of SASL mechanisms.
The following cluster properties are new in this version:
-
iceberg_backlog_controller_p_coeff
: Configures the coefficient for backlog control in Iceberg tables. -
iceberg_default_partition_spec
: Sets the default partition specification for Iceberg tables. -
iceberg_disable_snapshot_tagging
: Disables snapshot tagging in Iceberg. -
iceberg_invalid_record_action
: Specifies the action for handling invalid records in Iceberg. -
iceberg_rest_catalog_authentication_mode
: Defines the authentication mode for the Iceberg REST catalog. -
iceberg_rest_catalog_oauth2_server_uri
: Specifies the OAuth2 server URI for the Iceberg REST catalog. -
iceberg_target_backlog_size
: Sets the target backlog size for Iceberg. -
iceberg_target_lag_ms
: Configures the target lag (in milliseconds) for Iceberg.
-
log_compaction_adjacent_merge_self_compaction_count
: Adjusts the number of self-compaction merges during log compaction.
-
raft_max_buffered_follower_append_entries_bytes_per_shard
: Limits the maximum bytes buffered for follower append entries per shard. -
raft_max_inflight_follower_append_entries_requests_per_shard
: Replaces the deprecatedraft_max_concurrent_append_requests_per_follower
to limit in-flight follower append requests per shard.
-
topic_partitions_memory_allocation_percent
: Adjusts the percentage of memory allocated for topic partitions.
-
storage_read_readahead_count
: Reduced default from10
to1
to optimize read throughput and minimize unaccounted memory usage, lowering the risk of OOM errors on local storage paths. -
topic_partitions_per_shard
: Increased default from1000
to5000
to support larger partition counts per shard.
The following client configuration properties were deprecated in version 24.2.1, and have been removed in this release:
-
kafka_client_group_byte_rate_quota
-
kafka_client_group_fetch_byte_rate_quota
-
target_quota_byte_rate
-
target_fetch_quota_byte_rate
-
kafka_admin_topic_api_rate
Use rpk cluster quotas
to manage client throughput limits based on the Kafka API.