- 8月 08, 2022
-
-
由 Aneesh Garg 创作于
Jira: https://confluentinc.atlassian.net/browse/KSECURITY-483 Migrating log4j12 to reload4j Migrating slf4j-log4j12 to slf4j-reload4j.jar
- 8月 04, 2022
-
-
由 Aneesh Garg 创作于
Jira: https://confluentinc.atlassian.net/browse/KSECURITY-509 Upgrading netty to v4.1.79.Final
-
- 7月 29, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 7月 17, 2022
-
-
由 Lucas Bradstreet 创作于
With 6f81bb18 merged, we can now use c4.xlarge instances with our system tests, which are much more reliable for spot than m3.xlarge.
-
- 7月 09, 2022
-
-
由 Lucas Bradstreet 创作于
When running with 4th generation instances supporting EBS only, we need to use a larger volume or else we run out of disk space during a system test run. This change also parameterizes the instance type as an env variable for easier testing. Reviewers: David Jacot <djacot@confluent.io>
-
- 6月 30, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 6月 16, 2022
-
-
由 Bruno Cadonna 创作于
With newer ducktape versions than < 0.9 system tests may run into authentication issues with the AK system test infrastructure. The version will be bumped up once we have infrastructure in place for newer paramiko versions brought in by ducktape 0.9. Reviewers: Lucas Bradstreet <lucas@confluent.io>, Matthias J. Sax <mjsax@apache.org>, Kvicii <Karonazaba@gmail.com>
-
- 5月 04, 2022
-
-
由 Purshotam Chauhan 创作于
-
- 4月 27, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 4月 11, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 3月 25, 2022
-
-
-
由 Randall Hauch 创作于
The `retryEndOffsets(…)` method in `TopicAdmin` recently added (KAFKA-12879, #11797) to allow the `KafkaBasedLog.start()` method to retry any failures reading the last offsets for a topic. However, this introduce a regression when talking to older brokers (0.10.x or earlier). The `KafkaBasedLog` already had logic that expected an `UnsupportedVersionException` thrown by the admin client when a Kafka API is not available on an older broker, but the new retry logic in `TopicAdmin` did not account for this and wrapped the exception, thereby breaking the `KafkaBasedLog` logic and preventing startup. The fix is to propagate this `UnsupportedVersionException` from the `TopicAdmin.retryEndOffsets(…)` method. Added a new unit test that first replicated the problem before the fix, and verified the fix corrects the problem.
-
- 3月 16, 2022
-
-
由 Jason Gustafson 创作于
It is possible to clean a segment partially if the offset map is filled before reaching the end of the segment. The highest offset that is reached becomes the new dirty offset after the cleaning completes. The data above this offset is nevertheless copied over to the new partially cleaned segment. Hence we need to ensure that the transaction index reflects aborted transactions from both the cleaned and uncleaned portion of the segment. Prior to this patch, this was not the case. We only collected the aborted transactions from the cleaned portion, which means that the reconstructed index could be incomplete. This can cause the aborted data to become effectively committed. It can also cause the deletion of the abort marker before the corresponding data has been removed (i.e. the aborted transaction becomes hanging). Reviewers: Jun Rao <junrao@gmail.com>
-
- 3月 11, 2022
-
-
由 Stanislav Vodetskyi 创作于
Ensures we always have the latest published ducktape version. This way whenever we release a new one, we won't have to cherry pick a bunch of commits across a bunch of branches.
-
- 3月 10, 2022
-
-
-
由 Randall Hauch 创作于
-
由 Philip Nee 创作于
This is an addendum to the KAFKA-12879 (#11797) to fix some tests that are somewhat flaky when a build machine is heavily loaded (when the timeouts are too small). - Add an if check to void sleep(0) - Increase timeout in the tests
-
由 Philip Nee 创作于
KAFKA-12879: Revert changes from KAFKA-12339 and instead add retry capability to KafkaBasedLog (#11797) Fixes the compatibility issue regarding KAFKA-12879 by reverting the changes to the admin client from KAFKA-12339 (#10152) that retry admin client operations, and instead perform the retries within Connect's `KafkaBasedLog` during startup via a new `TopicAdmin.retryEndOffsets(..)` method. This method delegates to the existing `TopicAdmin.endOffsets(...)` method, but will retry on `RetriableException` until the retry timeout elapses. This change should be backward compatible to the KAFKA-12339 so that when Connect's `KafkaBasedLog` starts up it will retry attempts to read the end offsets for the log's topic. The `KafkaBasedLog` existing thread already has its own retry logic, and this is not changed. Added more unit tests, and thoroughly tested the new `RetryUtil` used to encapsulate the parameterized retry logic around any supplied function.
-
- 2月 11, 2022
-
-
-
由 prince-mahajan 创作于
KAFKA-13636: Fix for the group coordinator issue where the offsets are deleted for unstable groups (#11742) This patch ensures that the committed offsets are not expired while the group is rebalancing. The issue is that we can't rely on the subscribed topics if the group is not stable. Reviewers: David Jacot <djacot@confluent.io>
-
- 1月 27, 2022
-
-
由 David Jacot 创作于
Reviewers: Manikumar Reddy
-
- 1月 25, 2022
-
-
由 David Jacot 创作于
Conflicts: gradle/dependencies.gradle
-
由 David Jacot 创作于
Changelog: https://github.com/netty/netty/issues?q=is%3Aclosed+milestone%3A4.1.73.Final Reviewers: Manikumar Reddy <manikumar.reddy@gmail.com>
-
- 1月 20, 2022
-
-
-
由 David Jacot 创作于
Release notes: https://github.com/eclipse/jetty.project/releases/tag/jetty-9.4.44.v20210927 Reviewers: Rajini Sivaram <rajinisivaram@googlemail.com>
-
- 12月 23, 2021
-
-
-
由 jiangyuan 创作于
Reviewers: Jun Rao <junrao@gmail.com>
-
- 12月 18, 2021
-
-
由 Confluent Jenkins Bot 创作于
-
- 12月 16, 2021
-
-
-
由 Bruno Cadonna 创作于
grgit 4.1.0 caused the following error with gradle > Could not resolve all artifacts for configuration ':classpath'. > Could not resolve org.eclipse.jgit:org.eclipse.jgit:latest.release. Required by: project : > org.ajoberstar.grgit:grgit-core:4.1.0 ... grgit 4.1.1 fixed this issue. Reviewers: David Jacot <david.jacot@gmail.com>
-
由 Prateek Agarwal 创作于
Allow the leader epoch to be re-assigned to the new value from the Metadata response if `oldTopicId` is not present in the cache. This is needed because `oldTopicId` is removed from the cache if the topic gets deleted but the leader epoch is not removed. Hence, metadata for the newly recreated topic won't be accepted unless we allow `oldTopicId` to be null. Reviewers: Jason Gustafson <jason@confluent.io>, David Jacot <djacot@confluent.io>
-
- 12月 10, 2021
-
-
由 Dejan Stojadinović 创作于
They're no longer used and JFrog is sunsetting JCenter. https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter Reviewers: Ismael Juma <ismael@juma.me.uk>
-
- 12月 02, 2021
-
-
由 Bruno Cadonna 创作于
A new version of JGit that is used by grgit that is used by gradle causes the following error: org/eclipse/jgit/storage/file/FileRepositoryBuilder has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 The reason is that version 6.0.0.202111291000-r of JGrit was compiled with a newer Java version than Java 8, probably Java 11. Explicitly setting the version of JGrit in gradle to 5.12.0.202106070339-r fixes the issue. Reviewers: David Jacot <djacot@confluent.io>, Ismael Juma <ismael@juma.me.uk>, Alexander Stohr, David Arthur <mumrah@gmail.com>
-
- 11月 17, 2021
-
-
- 11月 16, 2021
-
-
由 Randall Hauch 创作于
This reverts commit 047ad654.
-
-
由 Luke Chen 创作于
This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
-
-
由 Justine Olshan 创作于
Store topic ID info in consumer metadata. We will always take the topic ID from the latest metadata response and remove any topic IDs from the cache if the metadata response did not return a topic ID for the topic. The benefit of this is that it lets us detect topic recreations. This allows the client to update metadata even if the leader epoch is lower than what was seen previously. Reviewers: Luke Chen <showuon@gmail.com>, Jason Gustafson <jason@confluent.io>
-