New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KAFKA-14275: KRaft Controllers should crash after failing to apply any metadata record #12709
KAFKA-14275: KRaft Controllers should crash after failing to apply any metadata record #12709
Conversation
Thanks, @niket-goel.
|
Thanks for the review @cmccabe
Agreed! I don't think I changed that. Please let me know if I did.
Sounds good. I will add it back in.
Yeah, I guess that is one way of doing it. Will play around to get a test in the next iteration. |
…y metadata record Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller.
8f81299
to
64d6396
Compare
The two tests that are failing in the build pass locally reliably:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a minor comment. LGTM overall.
} | ||
} | ||
|
||
private final static List<ApiMessageAndVersion> CORRUPT_RECORD = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: perhaps better to call this INVALID_RECORD
with a brief comment mentioning the topicId is not set. Also, since it's not used in any other tests, maybe we can keep it local to testFatalMetadataReplayErrorOnStandbys
? It's always possible to factor it out if it does get used in other tests.
…fault-handling Detect faults on nodes individually
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The failed tests (5) on the most recent version of the PR seem unrelated and flaky. |
Two different tests failing this time (timeout and metric not updated)
|
…y metadata record (apache#12709) Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller. This prevents a standby controller from eventually becoming active with incomplete state. Reviewers: Colin Patrick McCabe <cmccabe@apache.org>, Jason Gustafson <jason@confluent.io> (cherry picked from commit 98a3dcb)
…y metadata record (#12709) Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller. This prevents a standby controller from eventually becoming active with incomplete state. Reviewers: Colin Patrick McCabe <cmccabe@apache.org>, Jason Gustafson <jason@confluent.io>
…y metadata record (apache#12709) Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller. This prevents a standby controller from eventually becoming active with incomplete state. Reviewers: Colin Patrick McCabe <cmccabe@apache.org>, Jason Gustafson <jason@confluent.io>
…y metadata record (apache#12709) Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller. This prevents a standby controller from eventually becoming active with incomplete state. Reviewers: Colin Patrick McCabe <cmccabe@apache.org>, Jason Gustafson <jason@confluent.io>
…y metadata record (apache#12709) (#48) Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller. This prevents a standby controller from eventually becoming active with incomplete state. Reviewers: Colin Patrick McCabe <cmccabe@apache.org>, Jason Gustafson <jason@confluent.io> Co-authored-by: Niket <niket-goel@users.noreply.github.com>
Make all faults in metadata processing on standby controllers be fatal. This is the same behavior-wise as the active controller.