-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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-13694: When the Broker side processes the ProduceRequest, it prints more specific information when the verification record fails. #11830
Conversation
… cpu and traffic on the broker side increase sharply JIRA link : https://issues.apache.org/jira/browse/KAFKA-13310 Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
…sets method JIRA link : https://issues.apache.org/jira/browse/KAFKA-13310 Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
2. Optimize the import of package Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
add test Method "testForceMetadataDeleteForPatternSubscriptionDuringRebalance()" Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 <riven.sun@zoom.us> Reviewers: Luke Chen <showuon@gmail.com>
Author: RivenSun2 riven.sun@zoom.us
� Conflicts: � clients/src/test/java/org/apache/kafka/clients/consumer/KafkaConsumerTest.java
…ints more specific information when the verification record fails. Story JIRA: https://issues.apache.org/jira/browse/KAFKA-13694
Hi @guozhangwang @showuon |
Thanks @RivenSun2 , the changes LGTM. |
Looked into the jenkins and they are irrelevant. Merging to trunk. |
Hi @guozhangwang |
JIRA status updated. Thanks for the contribution! |
@@ -571,13 +571,9 @@ private[log] object LogValidator extends Logging { | |||
private def processRecordErrors(recordErrors: Seq[ApiRecordError]): Unit = { | |||
if (recordErrors.nonEmpty) { | |||
val errors = recordErrors.map(_.recordError) | |||
if (recordErrors.exists(_.apiError == Errors.INVALID_TIMESTAMP)) { |
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.
We do we no longer need this special case?
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.
Yes, looks like we need this, because we break 2 test cases after removing it. PR to bring it back to fix failed tests is opened: #11853 . Thanks.
When the Broker side processes the ProduceRequest, it prints more specific information when the verification record fails.
Story JIRA: https://issues.apache.org/jira/browse/KAFKA-13694