Skip to content
代码片段 群组 项目
  1. 8月 08, 2022
  2. 8月 04, 2022
  3. 7月 29, 2022
  4. 7月 17, 2022
  5. 7月 09, 2022
  6. 6月 30, 2022
  7. 6月 16, 2022
    • Bruno Cadonna's avatar
      MINOR: Pin ducktape version to < 0.9 (#12242) · 8fa6b36d
      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>
      8fa6b36d
  8. 5月 04, 2022
  9. 4月 27, 2022
  10. 4月 11, 2022
  11. 3月 25, 2022
    • Confluent Jenkins Bot's avatar
    • Randall Hauch's avatar
      KAFKA-13770: Restore compatibility with KafkaBasedLog using older Kafka brokers (#11946) · 4eb0aeec
      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.
      4eb0aeec
  12. 3月 16, 2022
    • Jason Gustafson's avatar
      KAFKA-13727; Preserve txn markers after partial segment cleaning (#11891) · 18cb82a3
      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>
      18cb82a3
  13. 3月 11, 2022
  14. 3月 10, 2022
    • Confluent Jenkins Bot's avatar
    • Randall Hauch's avatar
      KAFKA-12879: Remove extra sleep (#11872) · d6525839
      Randall Hauch 创作于
      d6525839
    • Philip Nee's avatar
      KAFKA-12879: Addendum to reduce flakiness of tests (#11871) · 0b53da0b
      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
      0b53da0b
    • Philip Nee's avatar
      KAFKA-12879: Revert changes from KAFKA-12339 and instead add retry capability... · 346cc48d
      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.
      346cc48d
  15. 2月 11, 2022
  16. 1月 27, 2022
  17. 1月 25, 2022
  18. 1月 20, 2022
  19. 12月 23, 2021
  20. 12月 18, 2021
  21. 12月 16, 2021
  22. 12月 10, 2021
  23. 12月 02, 2021
    • Bruno Cadonna's avatar
      HOTFIX: Set version of jgit to avoid unsupported version error (#11554) · 31fa971a
      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>
      31fa971a
  24. 11月 17, 2021
  25. 11月 16, 2021
加载中