Skip to content

Releases: linkedin/kafka

fix for KAFKA-8950 - KafkaConsumer stops fetching

15 Apr 22:17
09d704e
Compare
Choose a tag to compare
2.0.0.25

[LI-HOTFIX] back-port the fix for KAFKA-8950 - KafkaConsumer stops fe…

Cache the UpdateMetadataRequest when using the latest inter broker protocol version

23 Mar 16:39
dc6b292
Compare
Choose a tag to compare

This release adds support for caching the UpdateMetadataRequest on the controller, with the goal of reducing the controller's memory footprint.
In order to use this feature for an existing cluster,

  1. run a rolling bounce of the cluster so this code is deployed
  2. change the inter.broker.protocol.version to be at least "2.5-IV0" for all brokers
  3. run a rolling bounce of the cluster again

Implementation of recycling memory pool.

18 Feb 19:56
42673dc
Compare
Choose a tag to compare

Pick up the patch:
Implementation of recycling memory pool. (#72)

Add OneAboveMinIsrCounter sensor.

31 Jan 21:51
5069ba4
Compare
Choose a tag to compare

Pick up the patch:
[LI-HOTFIX] Add OneAboveMinIsrCounter sensor. (#71)

Added support to enable passthrough mirroring data from V1 format to V2 format

29 Jan 17:03
Compare
Choose a tag to compare

Pass through mirroring as it is today, works when the log.message.format.version between source and destination cluster is the same (0.10.0 to 0.10.0, 2.0 to 2.0). When there is a mixed message format between source and destination, KMM throws errors.
This patch makes passthrough mirroring work when the source is at 0.10.0 format and destination is at 2.0 format.
This patch does not address the errors/issues when the source is at 2.0 format and destination is at 0.10.0 format.

Fix SSL channel close on fake buffer overflow/underflow

17 Jan 00:52
4a0ec76
Compare
Choose a tag to compare

Pick up the patch:
[LI-HOTFIX] Fix SSL channel close on fake buffer overflow/underflow (#62)

Be ultra lazy in loading lazy indices during index deletion.

07 Jan 23:26
da84506
Compare
Choose a tag to compare

Avoid initialization of logSegment indices during deleteIfExists in case the logSegment indices have not been initialized before. This helps with overall resource usage of Kafka server, as well as prevents flaky errors while deleting log segments due to java.io.IOException: No such file or directory.

Pick up KAFKA-8104 and KAFKA-9156

07 Jan 21:23
40065ac
Compare
Choose a tag to compare

Multiple patches are cherry picked:

  • [LI-CHERRY-PICK][dca1bf1] Fix LazyTimeIndex & LazyOffsetIndex concurrency (#67)
  • [LI-HOTFIX] pick up KAFKA-8104 with modification (#66)

Improve shutdown time and resource allocation, pick up bug fixes.

21 Dec 01:29
12417cc
Compare
Choose a tag to compare
  • [LI-HOTFIX] Improve shutdown performance via lazy accessing the offset and time indices. (#65)
  • [LI-HOTFIX] Fix typo in docString of UpdateMetadataRequest. (#55)
  • [LI-HOTFIX] Guard costly trace- and debug-level logging to avoid unnecessary resource use during index operations. (#64)
  • [LI-HOTFIX] Rollback hotfix to pick up fix for KAFKA-9212 and KAFKA-9261. (#63)
  • [LI-HOTFIX] Remove KafkaZkClient#setOrCreatePartitionReassignment and add AdminZkClient#addPartitions (#60)

[LI-HOTFIX] Rollback KAFKA-7440 as a workaround for KAFKA-9212.

05 Dec 01:22
c432d86
Compare
Choose a tag to compare

TICKET =
LI_DESCRIPTION =
Client-side rollback for sending leader epoch to avoid receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest.
EXIT_CRITERIA = TICKET [KAFKA-9212]