v21.11.4

[ivotron]

Bug fixes

• Editing additionalConfiguration in CR does not restart redpanda and apply config #2619 k8s: After cluster config is changed in CR, the redpanda pods will get restarted for the config to get used. Beware that updating to this version of operator will always trigger one restart of your managed redpanda clusters after it's updated. by @alenkacz in Backport fix for #2619 #3723
• test: NodesDecommissioningTest.test_decommissioning_working_node test failure #3277 ducktape failure in test_recovery_after_catastrophic_failure #3328 Fixes for node decommissioning in face of failures. by @mmaslankaprv in Backporting #3355 #3487 #3631
• cloud_storage: assertion in manifest.cc "Local manifest and remote doesn't match" #3316 Fix shadow indexing error that occurred when the partition was moved between the nodes. by @Lazin in Backporting #3492 (Use stable paths in s3) #3632
• cloud_storage: rapidjson segfault on low memory #3429 json: use throwing allocator for rapid_json Writer #3561 Better stack traces in case of crash on low memory. by @LenaAn in V21.11.x backport3570 #3672
• cluster: Stale leadership in partition_leaders_table on leader (failure in ClusterConfigTest.test_restart) #3486 Fix an issue where nodes may have stale leadership metadata for a short period after a node restarts. by @mmaslankaprv in Backporting #3355 #3487 #3631
• Shadow indexing memory fragmentation #3548 Shadow indexing memory utilization was optimised. by @Lazin in Backport #3607 (Improve SI memory layout) #3660
• Operator should prevent reducing the number of cores #3639 k8s operator: the webhook now guards against decrease of the number of assigned cores. by @nicolaferraro in Backport fix for #3639 #3724
• Backports for Pandaproxy fixes to v21.11.x #3649 Pandaproxy: An inactive consumer is now timed out after pandaproxy.consumer_instance_timeout_ms. by @BenPope in Backport v21.11.x pandaproxy schema registry #3673
• Backports for Pandaproxy fixes to v21.11.x #3649 Pandaproxy: Creating a consumer with an existing name now fails with {"error_code": 40902}. by @BenPope in Backport v21.11.x pandaproxy schema registry #3673
• Backports for Pandaproxy fixes to v21.11.x #3649 Pandaproxy: Improve header validation and Swagger API. by @BenPope in Backport v21.11.x pandaproxy schema registry #3673
• Backports for Schema Registry fixes to v21.11.x #3650 Schema Registry: Fix a crash when publishing multiple protobuf schema. by @BenPope in Backport v21.11.x pandaproxy schema registry #3673
• Backports for Schema Registry fixes to v21.11.x #3650 Schema Registry: Support protobuf encoded protobuf schema for compatibility with Protobuf Serializers. by @BenPope in Backport v21.11.x pandaproxy schema registry #3673
• Fixed cleanup policy application when using cloud storage or transactions. by @mmaslankaprv in Backport of #3743, #3732 #3758
• Fixed error preventing redpanda from starting if the only partition movement operation involved x-core move. by @mmaslankaprv in Backport of #3558 #3617 #3671 #3674
• Fixed metadata dissemination in newly created clusters. by @mmaslankaprv in Backport of #3558 #3617 #3671 #3674
• Fixes a panic in rpk group seek if there was an error during the offset commit. by @twmb in backport/V21.11.x group patch #3759
• Not forcing consumers to rejoin group when transferring group partition leadership. by @mmaslankaprv in Backport of #3743, #3732 #3758

Features

• Move usage stats reporting into redpanda #2707 Metrics reporter. by @mmaslankaprv in Metrics reporter backport  #3727

Full Changelog: v21.11.3...v21.11.4

---

This discussion was created from the release v21.11.4.