redpanda-data/redpanda v22.3.16

on GitHub

Bug Fixes

• Fix a rare race between segment rolling and the readers cache which caused spurious, temporary dead-locks by @VladLazar in #9708
• Fix cases where sending very large batches to compacted topics using LZ4 or gzip compression could result in bad_alloc errors. by @jcsp in #9722
• Fix offset translation failure that could be triggered after topic recovery by @Lazin in #9872
• Fix race between compaction and application of retention to the local log. This occurred when compaction
  happened below the start offset of the log. It did not have a noticeable impact upon user workloads. by @VladLazar in #9612
• Fixed excessive kvstore writes that could lead to memory fragmentation issues during heavy produce load. by @ztlpn in #9962
• Fixes a bug in our http client that may crash redpanda in exceptional cases by @graphcareful in #9924
• #10037 Fixed issue where Redpanda will assert if data being consumed by Pandaproxy is not JSON serializable by @michael-redpanda in #10039
• #8987 An issue is fixed where a cluster might not activate new functionality after an upgrade if a controller leadership change happened at a particular point during upgrade by @jcsp in #8988
• #9513 Fixed a bug that would result in read replicas reporting a high watermark that was too high. by @andrwng in #9727
• #9680 fixes an assertion that may happen when Raft snapshot is delivered to recover follower having any of rm tx or id_allocator stms by @mmaslankaprv in #9681
• #9861 fix consumer group kafka incompatibilities (update offset_fetch to return committed_leader_epoch) by @rystsov in #9862
• #9875 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 #9876
• #9875 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 #9876

Improvements

• Admn API: GET /v1/security/users excludes ephemeral users unless specified otherwise. by @BenPope in #9957
• Duplicate PUT/POST/DELETE admin API requests for user management are now handled more efficiently. by @jcsp in #9856
• Improves memory management with transactions and idempotency by avoiding large contiguous allocations. by @bharathv in #9632
• Partition movements will not automatically make the partition under replicated by @mmaslankaprv in #9510
• Reduced memory consumption on configurations with very large numbers of small segments. by @jcsp in #10044
• #9825 schema_registry: Allow a schema id and version to be supplied by @BenPope in #9828
• rpk: decommission command fails with a friendly message when a node is dead by @daisukebe in #9699

Full Changelog: v22.3.15...v22.3.16