update to latest #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Regression from f19a31d.
…efalut value - fixed that.
in rd_kafka_CreateAclsResponse_parse rd_list
Not resetting the signalled event caused the next call(s) to WSAWaitForMultipleEvents() to wake-up immediately, causing increased CPU usage.
…osed() This is mainly for the Go client, but can be used by applications as well.
On m1 MacOS homebrew is located in a different place, so configure script is not able to locate libssl and libcrypto. This change makes it possible to use those libraries during build on M1.
Metadata cache was cleared on full metadata refresh, leading to unnecessary refreshes and occasional `UNKNOWN_TOPIC_OR_PART` errors. Solved by updating cache for existing or hinted entries instead of clearing them. Happening since 2.1.0
…g a consumer group (#4678) A metadata call before member joins consumer group, could lead to an `UNKNOWN_TOPIC_OR_PART` error. Solved by updating the consumer group following a metadata refresh only in safe states. Happening since 2.1.0
Metadata refreshes without partition leader change could lead to a loop of metadata calls at fixed intervals. Solved by stopping metadata refresh when all existing metadata is non-stale. Happening since 2.3.0
- rename 'generic' protocol to 'classic'
- consumer group serve timer to awake the loop earlier
- compare and find into topic partition list by topic id only
- fix memory leak when instance creation fails and app_conf is provided
- fix cases where HB response is received after unsubscription
- use topic name from current assignment if it's missing from metadata
- expedite heartbeat simplification and
fixes to next interval check and to the place where
number of retries is increased
- expedite HB after changing state back to INIT
- use the CONSUMER_F_WAIT_REJOIN to trigger
the rejoin instead of calling it from max poll interval timer
- schedule timer for next execution
reschedule it if expected earlier
expedite through scheduling cgrp serve timer
- treat unsupported feature error
as fatal
- avoid removing partitions not matched by a new subscription
immediately, for a possible desynchronization with the coordinator,
with said partitions not being consumed anymore
…ch (#4681) - Added new errors to manual commit. - improvements to OffsetCommit and OffsetFetch error code handling.
…g of the response. (#4691)
A partition migration could happen, using stale metadata, when the partition was undergoing a validation and being retried because of an error. Solved by doing a partition migration only with a non-stale leader epoch. Happening since 2.1.0
While using the cooperative assignor, given an assignment is received while closing the consumer it's possible that it gets stuck in state WAIT_ASSIGN_CALL, while the method is converted to a full unassign. Solved by changing state from WAIT_ASSIGN_CALL to WAIT_UNASSIGN_CALL while doing this conversion. Closes #4527
C++ version fix Add space in warning
* Change retry.backoff.* to apply to both producer and consumer * Style fixes
* Metadata handler upgrade to version 12 and offset leader epoch fix in ListOffsets * Fixed tag for alpine and manylinux images * Update msys2 installer and fix for missing CURL_LIBRARIES * Fix request by topic name when topic id is available
* Add files for lz4 1.9.4 * Update changelog.md * rdxxhash should not be in clang-format list * Add instructions and update memory alloc/free * Update instructions for lz4
Remove kafka-eng as it's too wide.
Fixes a segfault when a segment is erased and more data is written to the buffer.
`resolve_canonical_bootstrap_servers_only` must only be used with Kerberos
…tructed identically when retried (#4750) Issues: #4736 Fix for an idempotent producer error, with a message batch not reconstructed identically when retried. Caused the error message "Local: Inconsistent state: Unable to reconstruct MessageSet". Happening on large batches. Solved by using the same backoff baseline for all messages in the batch. Happens since 2.2.0
- Style fix - RPC version update - Fix uninitialized value and topic name from rkt - Revert newline changes - Remove duplicate declaration - Rename rd_kafka_buf_write_tags to rd_kafka_buf_write_tags_empty before implementing the define that allows to write tags - Upgrade fetch mock handler to v15 - devel assertion and logging improvements Co-authored-by: Emanuele Sabellico <[email protected]>
client mock cluster implementation --------- Co-authored-by: Emanuele Sabellico <[email protected]>
and for tags common to Fetch and Produce in KIP-951 --------- Co-authored-by: mahajanadhitya <[email protected]> Co-authored-by: Emanuele Sabellico <[email protected]>
* update third party dependencies * update lz4 version in the header file * update libraries for the windows build * reverting the version bump in the headers * use the latest version of curl * Update OpenSSL and add CHANGELOG.md * downgade curl version to one available via vcpkg * downgrade zlib to last available version in vcpkg * downgrade zstd to the latest available * Include CPPFLAGS within make for libcurl * Update mklove/modules/configure.libcurl * Update CHANGELOG.md --------- Co-authored-by: Milind L <[email protected]> Co-authored-by: Emanuele Sabellico <[email protected]>
contains the code changes to trigger a metadata update when the corresponding tags are received by the broker for partitions that have changed leadership, during Fetch or Produce requests.
Version 2.5.0-RC1
* Add test and mock files * Remove unnecessary semicolons * Review comments: * Fix to reduce flakyness of test 0146/do_test_stale_metadata_doesnt_migrate_partition * CHANGELOG and INTRODUCTION documentation --------- Co-authored-by: Anchit Jain <[email protected]>
Later versions of zstd fail without -lrt, see facebook/zstd#3558 .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.