v23.1.7

[piyushredpanda]

Bug Fixes

• Fix cases where sending very large batches to compacted topics using LZ4 or gzip compression could result in bad_alloc errors. by @jcsp in #9721
• Fix offset translation failure that could be triggered after topic recovery by @Lazin in #9871
• Fixed a bug in which the segment merging could run from read replicas. by @andrwng in #9757
• Fixed another bug where multiple configuration updates would cause an inconsistency upon next reload of usage state by @graphcareful in #9965
• Fixed excessive kvstore writes that could lead to memory fragmentation issues during heavy produce load. by @ztlpn in #9960
• Fixes a bug in our http client that may crash redpanda in exceptional cases by @graphcareful in #9922
• Fixes a bug where usage_manger would report incorrect cloud storage metrics when queried on the leader node. by @graphcareful in #9965
• #10036 Fixed issue where Redpanda will assert if data being consumed by Pandaproxy is not JSON serializable by @michael-redpanda in #10038
• #10068 The vectorized_memory_available_memory metric is now available on the /metrics endpoint in addition to /public_metrics. by @travisdowns in #10069
• #9651 Improve precision of the adjacent segment merger to avoid unnecessary segment reuploads by @Lazin in #9845
• #9859 fix consumer group kafka incompatibilities (update offset_fetch to return committed_leader_epoch) by @rystsov in #9860
• #9873 An issue is fixed where time queries on tiered storage partitions could return -1 incorrectly if the queried timestamp was earlier than the start of the log. by @jcsp in #9874
• #9873 An issue is fixed where time queries on tiered storage partitions using offsets close to the end of the local raft log could sometimes return offsets slightly ahead of the correct offset, if the segment containing the correct offset had already been offloaded to object storage. by @jcsp in #9874
• operator: fixed an issue that caused continue reconciliations on the custom resource by @nicolaferraro in #9979

Improvements

• Adds a timeout parameter to transfer_leadership_request to change the recovery timeout. by @ballard26 in #10073
• Admn API: GET /v1/security/users excludes ephemeral users unless specified otherwise. by @BenPope in #9952
• Duplicate PUT/POST/DELETE admin API requests for user management are now handled more efficiently. by @jcsp in #9855
• Maximum throttle time for Kafka API requests reduced to 30s to avoid heartbeat timeouts in default client configurations. by @dlex in #9985
• Operator allows referencing secrets that do not yet exist as certificate holders for listeners by @nicolaferraro in #9898
• Reduced memory consumption on configurations with very large numbers of small segments. by @jcsp in #10043
• Spurious end_of_stream log messages under normal operation are reduced. by @jcsp in #9972
• String configuration properties which ought not to be set to an empty string are now validated as such. This reduces risk of issues from tools that might treat "" equivalently to not setting a property. by @jcsp in #9805
• #9810 The /v1/brokers admin API endpoint now includes the broker's internal_rpc_address and internal_rpc_port. by @jcsp in #9811
• #9825 schema_registry: Allow a schema id and version to be supplied by @BenPope in #9826

Full Changelog: v23.1.6...v23.1.7

---

This discussion was created from the release v23.1.7.