Skip to content

KAFKA-8586: Hot fix#239

Merged
Magesh Nandakumar (mageshn) merged 1 commit into
4.0.3-cp1from
4.0.3-cp1-KAFKA-8586
Nov 23, 2019
Merged

KAFKA-8586: Hot fix#239
Magesh Nandakumar (mageshn) merged 1 commit into
4.0.3-cp1from
4.0.3-cp1-KAFKA-8586

Conversation

@mageshn

@mageshn Magesh Nandakumar (mageshn) commented Nov 20, 2019

Copy link
Copy Markdown
Member

KAFKA-8586: Fail source tasks when producers fail to send records

Changed Connect's WorkerSourceTask to capture non-retriable exceptions from the producer.send(...) (e.g., authentication or authorization errors) and to fail the connector task when such an error is encountered. Modified the existing unit tests to verify this functionality.

Note that most producer errors are retriable, and Connect will (by default) set up each producer with 1 max in-flight message and infinite retries. This change only affects non-retriable errors.

(cherry picked from commit 3aa9f99)

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.

Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

…ache#6993)

Changed Connect's `WorkerSourceTask` to capture non-retriable exceptions from the `producer.send(...)` (e.g., authentication or authorization errors) and to fail the connector task when such an error is encountered. Modified the existing unit tests to verify this functionality.

Note that most producer errors are retriable, and Connect will (by default) set up each producer with 1 max in-flight message and infinite retries. This change only affects non-retriable errors.

(cherry picked from commit 3aa9f99)
@mageshn

Copy link
Copy Markdown
Member Author

Xin Xiang (@xiangxin72) can we get PR builder enabled for this?

@C0urante Chris Egerton (C0urante) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Would be nice if we could run the branch builder to verify but these changes mirror the code in AK/trunk almost exactly so if that's not possible I still believe this should be okay.

@xiangxin72 Xin Xiang (xiangxin72) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like we don't have a way to do PR build for old branch. Let's merge this in and use the packaging job to verify then (gonna take 5 hours though)

@mageshn
Magesh Nandakumar (mageshn) merged commit 03f1b1d into 4.0.3-cp1 Nov 23, 2019
Andrew Egelhofer (andrewegel) pushed a commit that referenced this pull request Nov 16, 2021
As we are stopping brokers in these tests, there is a timing issue where the TierTopicManager doesn't manage to create the tier topic and doesn't become ready in time to archive the segments we produce. By the time it tries to create the tier topic, there are not enough brokers for the replication factor, meaning that all tiering is blocked.

Also improve logging when tier topic creation fails.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants