Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #260

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 409270 lines...]
[2021-06-29T04:35:50.579Z] > Task :clients:compileTestJava UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :clients:testClasses UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :streams:test-utils:compileJava UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :metadata:compileJava UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :core:compileJava NO-SOURCE
[2021-06-29T04:35:50.579Z] > Task 
:streams:generateMetadataFileForMavenJavaPublication
[2021-06-29T04:35:50.579Z] > Task :connect:json:compileTestJava UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :connect:json:testClasses UP-TO-DATE
[2021-06-29T04:35:50.579Z] > Task :connect:json:testJar
[2021-06-29T04:35:50.579Z] > Task :connect:json:testSrcJar
[2021-06-29T04:35:50.579Z] > Task 
:clients:generateMetadataFileForMavenJavaPublication
[2021-06-29T04:35:51.513Z] > Task :core:compileScala UP-TO-DATE
[2021-06-29T04:35:51.513Z] > Task :core:classes UP-TO-DATE
[2021-06-29T04:35:51.513Z] > Task :core:compileTestJava NO-SOURCE
[2021-06-29T04:35:51.513Z] > Task :core:compileTestScala UP-TO-DATE
[2021-06-29T04:35:51.513Z] > Task :core:testClasses UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task :connect:api:javadoc
[2021-06-29T04:35:56.553Z] > Task :connect:api:copyDependantLibs UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task :connect:api:jar UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task 
:connect:api:generateMetadataFileForMavenJavaPublication
[2021-06-29T04:35:56.553Z] > Task :connect:json:copyDependantLibs UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task :connect:json:jar UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task 
:connect:json:generateMetadataFileForMavenJavaPublication
[2021-06-29T04:35:56.553Z] > Task :connect:api:javadocJar
[2021-06-29T04:35:56.553Z] > Task 
:connect:json:publishMavenJavaPublicationToMavenLocal
[2021-06-29T04:35:56.553Z] > Task :connect:json:publishToMavenLocal
[2021-06-29T04:35:56.553Z] > Task :connect:api:compileTestJava UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task :connect:api:testClasses UP-TO-DATE
[2021-06-29T04:35:56.553Z] > Task :connect:api:testJar
[2021-06-29T04:35:56.553Z] > Task :connect:api:testSrcJar
[2021-06-29T04:35:56.553Z] > Task 
:connect:api:publishMavenJavaPublicationToMavenLocal
[2021-06-29T04:35:56.553Z] > Task :connect:api:publishToMavenLocal
[2021-06-29T04:35:57.487Z] 
[2021-06-29T04:35:57.487Z] > Task :streams:javadoc
[2021-06-29T04:35:57.487Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java:142:
 warning - Tag @link: reference not found: Processor
[2021-06-29T04:35:57.487Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/ThreadMetadata.java:111:
 warning - Missing closing '}' character for inline tag: "{@code
[2021-06-29T04:35:57.487Z]  Objects.hash(
[2021-06-29T04:35:57.487Z]  threadName,
[2021-06-29T04:35:57.487Z]  threadState,
[2021-06-29T04:35:57.487Z]  activeTasks,
[2021-06-29T04:35:57.487Z]  standbyTasks,
[2021-06-29T04:35:57.487Z]  mainConsumerClientId,
[2021-06-29T04:35:57.487Z]  restoreConsumerClientId,
[2021-06-29T04:35:57.487Z]  producerClientIds,
[2021-06-29T04:35:57.487Z]  adminClientId);
[2021-06-29T04:35:57.487Z]  "
[2021-06-29T04:35:58.421Z] 2 warnings
[2021-06-29T04:35:59.355Z] 
[2021-06-29T04:35:59.355Z] > Task :streams:javadocJar
[2021-06-29T04:35:59.355Z] > Task :streams:compileTestJava UP-TO-DATE
[2021-06-29T04:35:59.355Z] > Task :streams:testClasses UP-TO-DATE
[2021-06-29T04:36:00.289Z] > Task :streams:testJar
[2021-06-29T04:36:00.289Z] > Task :streams:testSrcJar
[2021-06-29T04:36:00.289Z] > Task 
:streams:publishMavenJavaPublicationToMavenLocal
[2021-06-29T04:36:00.289Z] > Task :streams:publishToMavenLocal
[2021-06-29T04:36:02.037Z] > Task :clients:javadoc
[2021-06-29T04:36:03.137Z] > Task :clients:javadocJar
[2021-06-29T04:36:04.395Z] > Task :clients:testJar
[2021-06-29T04:36:04.395Z] > Task :clients:testSrcJar
[2021-06-29T04:36:04.395Z] > Task 
:clients:publishMavenJavaPublicationToMavenLocal
[2021-06-29T04:36:04.395Z] > Task :clients:publishToMavenLocal
[2021-06-29T04:36:04.395Z] 
[2021-06-29T04:36:04.395Z] Deprecated Gradle features were used in this build, 
making it incompatible with Gradle 8.0.
[2021-06-29T04:36:04.395Z] Use '--warning-mode all' to show the individual 
deprecation warnings.
[2021-06-29T04:36:04.395Z] See 
https://docs.gradle.org/7.0.2/userguide/command_line_interface.html#sec:command_line_warnings
[2021-06-29T04:36:04.395Z] 
[2021-06-29T04:36:04.395Z] Execution optimizations have been disabled for 2 
invalid unit(s) of work during this build to ensure correctness.
[2021-06-29T04:36:04.395Z] Please consult deprecation warnings for more details.
[2021-06-29T04:36:04.395Z] 
[2021-06-29T04:36:04.395Z] BUILD 

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #259

[Apache Jenkins Server]

See 

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #163

[Apache Jenkins Server]

See 


Changes:

[Matthias J. Sax] KAFKA-12951: restore must terminate for tx global topic 
(#10894)


--
[...truncated 3.45 MB...]

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordsFromKeyValuePairs STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordsFromKeyValuePairs PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithNullKeyAndDefaultTimestamp 
STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithNullKeyAndDefaultTimestamp 
PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithDefaultTimestamp 
STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithDefaultTimestamp 
PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithNullKey STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithNullKey PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateNullKeyConsumerRecordWithOtherTopicNameAndTimestampWithTimetamp 
STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateNullKeyConsumerRecordWithOtherTopicNameAndTimestampWithTimetamp 
PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordWithTimestamp STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordWithTimestamp PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullHeaders STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullHeaders PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithDefaultTimestamp STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithDefaultTimestamp PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicName STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicName PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithNullKey STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithNullKey PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecord STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecord PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateNullKeyConsumerRecord STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateNullKeyConsumerRecord PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordWithOtherTopicName STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldCreateConsumerRecordWithOtherTopicName PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > shouldAdvanceTime 
STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > shouldAdvanceTime 
PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithKeyValuePairs STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldNotAllowToCreateTopicWithNullTopicNameWithKeyValuePairs PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithKeyValuePairsAndCustomTimestamps
 STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithKeyValuePairsAndCustomTimestamps
 PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithKeyValuePairs 
STARTED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 
shouldRequireCustomTopicNameIfNotDefaultFactoryTopicNameWithKeyValuePairs PASSED

org.apache.kafka.streams.test.ConsumerRecordFactoryTest > 

[jira] [Resolved] (KAFKA-12631) Support api to resign raft leadership

[Jason Gustafson (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-12631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gustafson resolved KAFKA-12631.
-
Fix Version/s: 3.0.0
   Resolution: Fixed

> Support api to resign raft leadership
> -
>
> Key: KAFKA-12631
> URL: https://issues.apache.org/jira/browse/KAFKA-12631
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Jason Gustafson
>Assignee: Jason Gustafson
>Priority: Major
> Fix For: 3.0.0
>
>
> It is useful to allow the controller to explicitly resign after encountering 
> an error of some kind. The Raft state machine implements a Resigned state, 
> but it is only currently used during graceful shutdown.
> This work depends on both of the following jiras:
> - KAFKA-12342: Adds resign() api after merging MetaLogManager interface
> - KAFKA-12607: Adds support for granting votes while in the Resigned state



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Build failed in Jenkins: Kafka » kafka-2.4-jdk8 #28

[Apache Jenkins Server]

See 


Changes:

[Ismael Juma] KAFKA-12790: Remove 
SslTransportLayerTest.testUnsupportedTlsVersion (#10922)


--
[...truncated 5.95 MB...]
org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldPutWithUnknownTimestamp STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldPutWithUnknownTimestamp PASSED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldPutWindowStartTimestampWithUnknownTimestamp STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldPutWindowStartTimestampWithUnknownTimestamp PASSED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldReturnIsPersistent STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > 
shouldReturnIsPersistent PASSED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardClose 
STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardClose 
PASSED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardFlush 
STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardFlush 
PASSED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardInit 
STARTED

org.apache.kafka.streams.internals.WindowStoreFacadeTest > shouldForwardInit 
PASSED

org.apache.kafka.streams.MockTimeTest > shouldGetNanosAsMillis STARTED

org.apache.kafka.streams.MockTimeTest > shouldGetNanosAsMillis PASSED

org.apache.kafka.streams.MockTimeTest > shouldSetStartTime STARTED

org.apache.kafka.streams.MockTimeTest > shouldSetStartTime PASSED

org.apache.kafka.streams.MockTimeTest > shouldNotAllowNegativeSleep STARTED

org.apache.kafka.streams.MockTimeTest > shouldNotAllowNegativeSleep PASSED

org.apache.kafka.streams.MockTimeTest > shouldAdvanceTimeOnSleep STARTED

org.apache.kafka.streams.MockTimeTest > shouldAdvanceTimeOnSleep PASSED

org.apache.kafka.streams.TestTopicsTest > testNonUsedOutputTopic STARTED

org.apache.kafka.streams.TestTopicsTest > testNonUsedOutputTopic PASSED

org.apache.kafka.streams.TestTopicsTest > testEmptyTopic STARTED

org.apache.kafka.streams.TestTopicsTest > testEmptyTopic PASSED

org.apache.kafka.streams.TestTopicsTest > testStartTimestamp STARTED

org.apache.kafka.streams.TestTopicsTest > testStartTimestamp PASSED

org.apache.kafka.streams.TestTopicsTest > testNegativeAdvance STARTED

org.apache.kafka.streams.TestTopicsTest > testNegativeAdvance PASSED

org.apache.kafka.streams.TestTopicsTest > shouldNotAllowToCreateWithNullDriver 
STARTED

org.apache.kafka.streams.TestTopicsTest > shouldNotAllowToCreateWithNullDriver 
PASSED

org.apache.kafka.streams.TestTopicsTest > testDuration STARTED

org.apache.kafka.streams.TestTopicsTest > testDuration PASSED

org.apache.kafka.streams.TestTopicsTest > testOutputToString STARTED

org.apache.kafka.streams.TestTopicsTest > testOutputToString PASSED

org.apache.kafka.streams.TestTopicsTest > testValue STARTED

org.apache.kafka.streams.TestTopicsTest > testValue PASSED

org.apache.kafka.streams.TestTopicsTest > testTimestampAutoAdvance STARTED

org.apache.kafka.streams.TestTopicsTest > testTimestampAutoAdvance PASSED

org.apache.kafka.streams.TestTopicsTest > testOutputWrongSerde STARTED

org.apache.kafka.streams.TestTopicsTest > testOutputWrongSerde PASSED

org.apache.kafka.streams.TestTopicsTest > 
shouldNotAllowToCreateOutputTopicWithNullTopicName STARTED

org.apache.kafka.streams.TestTopicsTest > 
shouldNotAllowToCreateOutputTopicWithNullTopicName PASSED

org.apache.kafka.streams.TestTopicsTest > testWrongSerde STARTED

org.apache.kafka.streams.TestTopicsTest > testWrongSerde PASSED

org.apache.kafka.streams.TestTopicsTest > testKeyValuesToMapWithNull STARTED

org.apache.kafka.streams.TestTopicsTest > testKeyValuesToMapWithNull PASSED

org.apache.kafka.streams.TestTopicsTest > testNonExistingOutputTopic STARTED

org.apache.kafka.streams.TestTopicsTest > testNonExistingOutputTopic PASSED

org.apache.kafka.streams.TestTopicsTest > testMultipleTopics STARTED

org.apache.kafka.streams.TestTopicsTest > testMultipleTopics PASSED

org.apache.kafka.streams.TestTopicsTest > testKeyValueList STARTED

org.apache.kafka.streams.TestTopicsTest > testKeyValueList PASSED

org.apache.kafka.streams.TestTopicsTest > 
shouldNotAllowToCreateOutputWithNullDriver STARTED

org.apache.kafka.streams.TestTopicsTest > 
shouldNotAllowToCreateOutputWithNullDriver PASSED

org.apache.kafka.streams.TestTopicsTest > testValueList STARTED

org.apache.kafka.streams.TestTopicsTest > testValueList PASSED

org.apache.kafka.streams.TestTopicsTest > testRecordList STARTED

org.apache.kafka.streams.TestTopicsTest > testRecordList PASSED

org.apache.kafka.streams.TestTopicsTest > testNonExistingInputTopic STARTED

org.apache.kafka.streams.TestTopicsTest > testNonExistingInputTopic PASSED

org.apache.kafka.streams.TestTopicsTest > testKeyValuesToMap 

Jenkins build is unstable: Kafka » Kafka Branch Builder » 2.8 #42

[Apache Jenkins Server]

See 

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #258

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 477582 lines...]
[2021-06-28T23:18:35.228Z] > Task :connect:api:testClasses UP-TO-DATE
[2021-06-28T23:18:35.228Z] > Task :connect:api:testJar
[2021-06-28T23:18:35.228Z] > Task :connect:api:testSrcJar
[2021-06-28T23:18:36.264Z] > Task 
:connect:json:publishMavenJavaPublicationToMavenLocal
[2021-06-28T23:18:36.264Z] > Task :connect:json:publishToMavenLocal
[2021-06-28T23:18:36.264Z] > Task 
:connect:api:publishMavenJavaPublicationToMavenLocal
[2021-06-28T23:18:36.264Z] > Task :connect:api:publishToMavenLocal
[2021-06-28T23:18:37.494Z] 
[2021-06-28T23:18:37.494Z] > Task :streams:javadoc
[2021-06-28T23:18:37.494Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java:142:
 warning - Tag @link: reference not found: Processor
[2021-06-28T23:18:37.494Z] 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/streams/ThreadMetadata.java:111:
 warning - Missing closing '}' character for inline tag: "{@code
[2021-06-28T23:18:37.494Z]  Objects.hash(
[2021-06-28T23:18:37.494Z]  threadName,
[2021-06-28T23:18:37.494Z]  threadState,
[2021-06-28T23:18:37.494Z]  activeTasks,
[2021-06-28T23:18:37.494Z]  standbyTasks,
[2021-06-28T23:18:37.494Z]  mainConsumerClientId,
[2021-06-28T23:18:37.494Z]  restoreConsumerClientId,
[2021-06-28T23:18:37.494Z]  producerClientIds,
[2021-06-28T23:18:37.494Z]  adminClientId);
[2021-06-28T23:18:37.494Z]  "
[2021-06-28T23:18:37.503Z] [Checks API] No suitable checks publisher found.
[Pipeline] echo
[2021-06-28T23:18:37.504Z] Skipping Kafka Streams archetype test for Java 11
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[2021-06-28T23:18:38.588Z] 2 warnings
[2021-06-28T23:18:38.588Z] 
[2021-06-28T23:18:38.588Z] > Task :streams:javadocJar
[2021-06-28T23:18:40.768Z] > Task :clients:javadoc
[2021-06-28T23:18:40.768Z] > Task :clients:javadocJar
[2021-06-28T23:18:41.861Z] > Task :clients:testJar
[2021-06-28T23:18:43.801Z] > Task :clients:testSrcJar
[2021-06-28T23:18:43.801Z] > Task 
:clients:publishMavenJavaPublicationToMavenLocal
[2021-06-28T23:18:43.801Z] > Task :clients:publishToMavenLocal
[2021-06-28T23:19:01.705Z] > Task :core:compileScala
[2021-06-28T23:20:12.974Z] > Task :core:classes
[2021-06-28T23:20:12.974Z] > Task :core:compileTestJava NO-SOURCE
[2021-06-28T23:20:41.350Z] > Task :core:compileTestScala
[2021-06-28T23:21:33.343Z] > Task :core:testClasses
[2021-06-28T23:22:01.604Z] > Task :streams:compileTestJava
[2021-06-28T23:23:13.466Z] > Task :streams:testClasses
[2021-06-28T23:23:13.466Z] > Task :streams:testJar
[2021-06-28T23:23:13.466Z] > Task :streams:testSrcJar
[2021-06-28T23:23:13.467Z] > Task 
:streams:publishMavenJavaPublicationToMavenLocal
[2021-06-28T23:23:13.467Z] > Task :streams:publishToMavenLocal
[2021-06-28T23:23:13.467Z] 
[2021-06-28T23:23:13.467Z] Deprecated Gradle features were used in this build, 
making it incompatible with Gradle 8.0.
[2021-06-28T23:23:13.467Z] Use '--warning-mode all' to show the individual 
deprecation warnings.
[2021-06-28T23:23:13.467Z] See 
https://docs.gradle.org/7.0.2/userguide/command_line_interface.html#sec:command_line_warnings
[2021-06-28T23:23:13.467Z] 
[2021-06-28T23:23:13.467Z] Execution optimizations have been disabled for 2 
invalid unit(s) of work during this build to ensure correctness.
[2021-06-28T23:23:13.467Z] Please consult deprecation warnings for more details.
[2021-06-28T23:23:13.467Z] 
[2021-06-28T23:23:13.467Z] BUILD SUCCESSFUL in 5m 5s
[2021-06-28T23:23:13.467Z] 71 actionable tasks: 37 executed, 34 up-to-date
[Pipeline] sh
[2021-06-28T23:23:16.426Z] + grep ^version= gradle.properties
[2021-06-28T23:23:16.426Z] + cut -d= -f 2
[Pipeline] dir
[2021-06-28T23:23:17.108Z] Running in 
/home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/quickstart
[Pipeline] {
[Pipeline] sh
[2021-06-28T23:23:19.222Z] + mvn clean install -Dgpg.skip
[2021-06-28T23:23:21.553Z] [INFO] Scanning for projects...
[2021-06-28T23:23:21.553Z] [INFO] 

[2021-06-28T23:23:21.553Z] [INFO] Reactor Build Order:
[2021-06-28T23:23:21.553Z] [INFO] 
[2021-06-28T23:23:21.553Z] [INFO] Kafka Streams :: Quickstart   
 [pom]
[2021-06-28T23:23:21.553Z] [INFO] streams-quickstart-java   
 [maven-archetype]
[2021-06-28T23:23:21.553Z] [INFO] 
[2021-06-28T23:23:21.553Z] [INFO] < 
org.apache.kafka:streams-quickstart >-
[2021-06-28T23:23:21.553Z] 

[jira] [Created] (KAFKA-13006) Remove the method RaftClient.leaderAndEpoch

[Jose Armando Garcia Sancio (Jira)]

Jose Armando Garcia Sancio created KAFKA-13006:
--

 Summary: Remove the method RaftClient.leaderAndEpoch
 Key: KAFKA-13006
 URL: https://issues.apache.org/jira/browse/KAFKA-13006
 Project: Kafka
  Issue Type: Sub-task
Reporter: Jose Armando Garcia Sancio


The are semantic differences between {{RaftClient.leaderAndEpoch}} and 
{{RaftClient.Listener.handleLeaderChange}} specially when the raft client 
transition from follower to leader. To simplify the API, I think that we should 
remove the method {{RaftClient.leaderAndEpoch}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-13005) Support JBOD in kraft mode

[Colin McCabe (Jira)]

Colin McCabe created KAFKA-13005:


 Summary: Support JBOD in kraft mode
 Key: KAFKA-13005
 URL: https://issues.apache.org/jira/browse/KAFKA-13005
 Project: Kafka
  Issue Type: Improvement
Reporter: Colin McCabe






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-13004) Trogdor performance decreases sharply with large amounts of tasks.

[Scott Hendricks (Jira)]

Scott Hendricks created KAFKA-13004:
---

 Summary: Trogdor performance decreases sharply with large amounts 
of tasks.
 Key: KAFKA-13004
 URL: https://issues.apache.org/jira/browse/KAFKA-13004
 Project: Kafka
  Issue Type: Bug
  Components: tools
 Environment: We run our Trogdor clusters within Kubernetes.
Reporter: Scott Hendricks
Assignee: Scott Hendricks


As part of my performance tests, I am running 3000 workloads within Trogdor.  
The clients seem to be able to handle this fine, but when I go to reset and run 
the same test again, Trogdor seems sluggish.

Here are the steps to reproduce this:
 # Run 3000 workloads in Trogdor, a combination of Produce/Consume workloads.
 # Wait for the workloads to complete.
 # Run the DELETE API calls to destroy all 3000 workloads to reset for the next 
run.
 # Confirm via the API that there are no workloads defined in the system.
 # Run an additional 3000 workloads in Trogdor similar to step 1.

The Coordinator takes a long time to start the second batch of 3000. There 
seems to be some performance issue in the framework that will take a while to 
debug. At this point I don't know if it only affects the Coordinator, or if the 
Agents are affected as well. I do not currently have the time to look into 
this, so I am creating this issue to track it.

The workaround I am employing is destroying and recreating the Trogdor cluster 
in between test runs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #257

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 475662 lines...]
[2021-06-28T19:53:46.208Z] 
[2021-06-28T19:53:46.208Z] PlaintextConsumerTest > 
testPerPartitionLeadMetricsCleanUpWithAssign() PASSED
[2021-06-28T19:53:46.208Z] 
[2021-06-28T19:53:46.208Z] PlaintextConsumerTest > 
testConsumeMessagesWithCreateTime() STARTED
[2021-06-28T19:53:52.559Z] 
[2021-06-28T19:53:52.559Z] PlaintextConsumerTest > 
testConsumeMessagesWithCreateTime() PASSED
[2021-06-28T19:53:52.559Z] 
[2021-06-28T19:53:52.559Z] PlaintextConsumerTest > testAsyncCommit() STARTED
[2021-06-28T19:53:58.308Z] 
[2021-06-28T19:53:58.308Z] PlaintextConsumerTest > testAsyncCommit() PASSED
[2021-06-28T19:53:58.308Z] 
[2021-06-28T19:53:58.308Z] PlaintextConsumerTest > 
testLowMaxFetchSizeForRequestAndPartition() STARTED
[2021-06-28T19:55:09.400Z] 
[2021-06-28T19:55:09.400Z] PlaintextConsumerTest > 
testLowMaxFetchSizeForRequestAndPartition() PASSED
[2021-06-28T19:55:09.400Z] 
[2021-06-28T19:55:09.400Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnStopPolling() STARTED
[2021-06-28T19:55:26.482Z] 
[2021-06-28T19:55:26.482Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnStopPolling() PASSED
[2021-06-28T19:55:26.482Z] 
[2021-06-28T19:55:26.482Z] PlaintextConsumerTest > 
testMaxPollIntervalMsDelayInRevocation() STARTED
[2021-06-28T19:55:33.559Z] 
[2021-06-28T19:55:33.559Z] PlaintextConsumerTest > 
testMaxPollIntervalMsDelayInRevocation() PASSED
[2021-06-28T19:55:33.559Z] 
[2021-06-28T19:55:33.559Z] PlaintextConsumerTest > 
testPerPartitionLagMetricsCleanUpWithAssign() STARTED
[2021-06-28T19:55:40.294Z] 
[2021-06-28T19:55:40.294Z] PlaintextConsumerTest > 
testPerPartitionLagMetricsCleanUpWithAssign() PASSED
[2021-06-28T19:55:40.294Z] 
[2021-06-28T19:55:40.294Z] PlaintextConsumerTest > 
testPartitionsForInvalidTopic() STARTED
[2021-06-28T19:55:45.041Z] 
[2021-06-28T19:55:45.041Z] PlaintextConsumerTest > 
testPartitionsForInvalidTopic() PASSED
[2021-06-28T19:55:45.041Z] 
[2021-06-28T19:55:45.041Z] PlaintextConsumerTest > 
testMultiConsumerStickyAssignment() STARTED
[2021-06-28T19:56:14.850Z] 
[2021-06-28T19:56:14.850Z] PlaintextConsumerTest > 
testMultiConsumerStickyAssignment() PASSED
[2021-06-28T19:56:14.850Z] 
[2021-06-28T19:56:14.850Z] PlaintextConsumerTest > 
testPauseStateNotPreservedByRebalance() STARTED
[2021-06-28T19:56:20.236Z] 
[2021-06-28T19:56:20.236Z] PlaintextConsumerTest > 
testPauseStateNotPreservedByRebalance() PASSED
[2021-06-28T19:56:20.236Z] 
[2021-06-28T19:56:20.236Z] PlaintextConsumerTest > 
testFetchHonoursFetchSizeIfLargeRecordNotFirst() STARTED
[2021-06-28T19:56:27.309Z] 
[2021-06-28T19:56:27.309Z] PlaintextConsumerTest > 
testFetchHonoursFetchSizeIfLargeRecordNotFirst() PASSED
[2021-06-28T19:56:27.309Z] 
[2021-06-28T19:56:27.309Z] PlaintextConsumerTest > testSeek() STARTED
[2021-06-28T19:56:35.557Z] 
[2021-06-28T19:56:35.557Z] PlaintextConsumerTest > testSeek() PASSED
[2021-06-28T19:56:35.557Z] 
[2021-06-28T19:56:35.557Z] PlaintextConsumerTest > 
testConsumingWithNullGroupId() STARTED
[2021-06-28T19:56:45.955Z] 
[2021-06-28T19:56:45.955Z] PlaintextConsumerTest > 
testConsumingWithNullGroupId() PASSED
[2021-06-28T19:56:45.955Z] 
[2021-06-28T19:56:45.955Z] PlaintextConsumerTest > testPositionAndCommit() 
STARTED
[2021-06-28T19:56:51.412Z] 
[2021-06-28T19:56:51.412Z] PlaintextConsumerTest > testPositionAndCommit() 
PASSED
[2021-06-28T19:56:51.412Z] 
[2021-06-28T19:56:51.412Z] PlaintextConsumerTest > 
testFetchRecordLargerThanMaxPartitionFetchBytes() STARTED
[2021-06-28T19:56:57.043Z] 
[2021-06-28T19:56:57.043Z] PlaintextConsumerTest > 
testFetchRecordLargerThanMaxPartitionFetchBytes() PASSED
[2021-06-28T19:56:57.043Z] 
[2021-06-28T19:56:57.043Z] PlaintextConsumerTest > testUnsubscribeTopic() 
STARTED
[2021-06-28T19:57:02.450Z] 
[2021-06-28T19:57:02.450Z] PlaintextConsumerTest > testUnsubscribeTopic() PASSED
[2021-06-28T19:57:02.450Z] 
[2021-06-28T19:57:02.450Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnClose() STARTED
[2021-06-28T19:57:14.925Z] 
[2021-06-28T19:57:14.925Z] PlaintextConsumerTest > 
testMultiConsumerSessionTimeoutOnClose() PASSED
[2021-06-28T19:57:14.925Z] 
[2021-06-28T19:57:14.925Z] PlaintextConsumerTest > 
testFetchRecordLargerThanFetchMaxBytes() STARTED
[2021-06-28T19:57:18.482Z] 
[2021-06-28T19:57:18.482Z] PlaintextConsumerTest > 
testFetchRecordLargerThanFetchMaxBytes() PASSED
[2021-06-28T19:57:18.482Z] 
[2021-06-28T19:57:18.482Z] PlaintextConsumerTest > 
testMultiConsumerDefaultAssignment() STARTED
[2021-06-28T19:57:35.458Z] 
[2021-06-28T19:57:35.458Z] PlaintextConsumerTest > 
testMultiConsumerDefaultAssignment() PASSED
[2021-06-28T19:57:35.458Z] 
[2021-06-28T19:57:35.458Z] PlaintextConsumerTest > testAutoCommitOnClose() 
STARTED
[2021-06-28T19:57:41.487Z] 
[2021-06-28T19:57:41.487Z] PlaintextConsumerTest > testAutoCommitOnClose() 
PASSED
[2021-06-28T19:57:41.487Z] 

Build failed in Jenkins: Kafka » kafka-2.5-jdk8 #47

[Apache Jenkins Server]

See 


Changes:

[Ismael Juma] KAFKA-12790: Remove 
SslTransportLayerTest.testUnsupportedTlsVersion (#10922)


--
[...truncated 3.10 MB...]
org.apache.kafka.streams.TopologyTestDriverTest > shouldPopulateGlobalStore[Eos 
enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > shouldPopulateGlobalStore[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldThrowIfPersistentBuiltInStoreIsAccessedWithUntypedMethod[Eos enabled = 
false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldThrowIfPersistentBuiltInStoreIsAccessedWithUntypedMethod[Eos enabled = 
false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldAllowPrePopulatingStatesStoresWithCachingEnabled[Eos enabled = false] 
STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldAllowPrePopulatingStatesStoresWithCachingEnabled[Eos enabled = false] 
PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnCorrectPersistentStoreTypeOnly[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnCorrectPersistentStoreTypeOnly[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > shouldRespectTaskIdling[Eos 
enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > shouldRespectTaskIdling[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUseSourceSpecificDeserializers[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUseSourceSpecificDeserializers[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > shouldReturnAllStores[Eos 
enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > shouldReturnAllStores[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotCreateStateDirectoryForStatelessTopology[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotCreateStateDirectoryForStatelessTopology[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldApplyGlobalUpdatesCorrectlyInRecursiveTopologies[Eos enabled = false] 
STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldApplyGlobalUpdatesCorrectlyInRecursiveTopologies[Eos enabled = false] 
PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnAllStoresNames[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnAllStoresNames[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPassRecordHeadersIntoSerializersAndDeserializers[Eos enabled = false] 
STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPassRecordHeadersIntoSerializersAndDeserializers[Eos enabled = false] 
PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessConsumerRecordList[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessConsumerRecordList[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUseSinkSpecificSerializers[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUseSinkSpecificSerializers[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldFlushStoreForFirstInput[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldFlushStoreForFirstInput[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessFromSourceThatMatchPattern[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessFromSourceThatMatchPattern[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUpdateStoreForNewKey[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldUpdateStoreForNewKey[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldSendRecordViaCorrectSourceTopicDeprecated[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldSendRecordViaCorrectSourceTopicDeprecated[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateOnWallClockTime[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateOnWallClockTime[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > shouldSetRecordMetadata[Eos 
enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > shouldSetRecordMetadata[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForLargerValue[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForLargerValue[Eos enabled = 

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #162

[Apache Jenkins Server]

See 


Changes:

[Ismael Juma] KAFKA-12790: Remove 
SslTransportLayerTest.testUnsupportedTlsVersion (#10922)


--
[...truncated 3.46 MB...]
org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestampWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestampWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueIsEqualWithNullForCompareValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueIsEqualWithNullForCompareValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfTimestampIsDifferentForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfTimestampIsDifferentForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualWithNullForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualWithNullForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueIsEqualWithNullForCompareKeyValueWithProducerRecord 
STARTED

Re: [DISCUSS] KIP-501 Avoid out-of-sync or offline partitions when follower fetch requests are not processed in time

[Mohan Parthasarathy]

Hi Satish,


>
>
> >It is not clear to me whether Solution 2 can happen independently. For
> example, if the leader exceeds *leader.fetch.process.time.max.ms
> * due to a transient condition,
> should it relinquish leadership immediately ? That might be aggressive in
> some cases. Detecting that a leader is slow cannot be determined by just
> one occurrence, right ?
>
> Solution(2) is an extension to Solution(1) as mentioned earlier in the
> KIP. This config is applicable only if
> `follower.fetch.pending.reads.insync.enable` is set as true. I have
> also updated the config description in the KIP to make that clear.
> In our observations, we do not always see this behavior continuously.
> It occurs intermittently and makes all the other requests pile up in
> the request queue. Sometimes, the broker goes down and makes the
> partitions offline.  Users need to set the config based on their
> host's configuration and behavior. We can also think about extending
> this config based on others observations.
>
>
That clarification in the document helps. But then setting the first option
to true does not necessarily mean that the condition is happening. Did you
mean to say that relinquish the leadership if it is taking longer than
leader.fetch.process.time.max.ms AND there are fetch requests pending which
are >= log-end-offset of the earlier fetch request ?

-Thanks
Mohan

> Thanks,
> Satish.
>
> On Mon, 28 Jun 2021 at 04:36, Mohan Parthasarathy 
> wrote:
> >
> > Hi Satish,
> >
> > One small clarification regarding the proposal. I understand how Solution
> > (1) enables the other replicas to be chosen as the leader. But it is
> > possible that the other replicas may not be in sync yet and if unclean
> > leader election is not enabled, the other replicas may not become the
> > leader right ?
> >
> >  It is not clear to me whether Solution 2 can happen independently. For
> > example, if the leader exceeds *leader.fetch.process.time.max.ms
> > * due to a transient condition,
> > should it relinquish leadership immediately ? That might be aggressive in
> > some cases. Detecting that a leader is slow cannot be determined by just
> > one occurrence, right ?
> >
> > Thanks
> > Mohan
> >
> >
> > On Sun, Jun 27, 2021 at 4:01 AM Satish Duggana  >
> > wrote:
> >
> > > Hi Dhruvil,
> > > Thanks for looking into the KIP and providing your comments.
> > >
> > > There are two problems about the scenario raised in this KIP:
> > >
> > > a) Leader is slow and it is not available for reads or writes.
> > > b) Leader is causing the followers to be out of sync and cause the
> > > partitions unavailability.
> > >
> > > (a) should be detected and mitigated so that the broker can become a
> > > leader or replace with a different node if this node continues having
> > > issues.
> > >
> > > (b) will cause the partition to go under minimum ISR and eventually
> > > make that partition offline if the leader goes down. In this case,
> > > users have to enable unclean leader election for making the partition
> > > available. This may cause data loss based on the replica chosen as a
> > > leader. This is what several folks(including us) observed in their
> > > production environments.
> > >
> > > Solution(1) in the KIP addresses (b) to avoid offline partitions by
> > > not removing the replicas from ISR. This allows the partition to be
> > > available if the leader is moved to one of the other replicas in ISR.
> > >
> > > Solution (2) in the KIP extends solution (1) by relinquishing the
> > > leadership and allowing one of the other insync replicas to become a
> > > leader.
> > >
> > > ~Satish.
> > >
>

[jira] [Resolved] (KAFKA-12976) Remove UNSUPPORTED_VERSION error from delete topics call

[Jason Gustafson (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gustafson resolved KAFKA-12976.
-
Resolution: Fixed

> Remove UNSUPPORTED_VERSION error from delete topics call
> 
>
> Key: KAFKA-12976
> URL: https://issues.apache.org/jira/browse/KAFKA-12976
> Project: Kafka
>  Issue Type: Task
>Affects Versions: 3.0.0, 2.8.0
>Reporter: Justine Olshan
>Assignee: Justine Olshan
>Priority: Major
> Fix For: 3.0.0, 2.8.1
>
>
> Originally I thought it would be useful to have an unsupported version error 
> returned when the broker's IBP did not support the operation. However, this 
> error is transient and in the -case of describe topics, it may not be 
> accurate.- Additionally, unsupported version is not retriable when the 
> scenarios that see this likely should be. 
> I propose always returning UNKNOWN_TOPIC_ID error when the topic ID is not 
> found on the broker. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-13003) KafkaBroker advertises socket port instead of the configured advertised port

[Uwe Eisele (Jira)]

Uwe Eisele created KAFKA-13003:
--

 Summary: KafkaBroker advertises socket port instead of the 
configured advertised port
 Key: KAFKA-13003
 URL: https://issues.apache.org/jira/browse/KAFKA-13003
 Project: Kafka
  Issue Type: Bug
  Components: core
Affects Versions: 2.8.0
Reporter: Uwe Eisele
Assignee: Uwe Eisele


In Kraft mode Apache Kafka 2.8.0 does advertise the socket port instead of the 
configured advertised port.

A broker given with the following configuration
{code:java}
listeners=PUBLIC://0.0.0.0:19092,REPLICATION://0.0.0.0:9091
advertised.listeners=PUBLIC://envoy-kafka-broker:9091,REPLICATION://kafka-broker1:9091
{code}
advertises on the _PUBLIC_ listener _envoy-kafka-broker:19092_, however I would 
expect that _envoy-kafka-broker:9091_ is advertised. In ZooKeeper mode it works 
as expected.

In a deployment with a L4 proxy in front of the Kafka cluster, it is important, 
that the advertised port can be different from the actual socket port.

I tested it with a Docker-Compose setup which runs 3 Kafka Broker in Kraft mode 
and an Envoy proxy in front of them. With Apache Kafka 2.8.0 it does not work, 
because Kafka does not advertise the configured advertised port. For more 
details see: 
https://github.com/ueisele/kafka/tree/fix/kraft-advertisedlisteners-build/proxy-examples/proxyl4-kafkakraft-bug-2.8

_Client -- 909[1-3] --> Envoy Proxy -- 19092 --> Kafka Broker [1-3]_

|| Envoy Host || Envoy Port || Kafka Broker || Kafka Port || Advertised 
Listener ||
| envoy-kafka-broker | 9091 | kafka-broker1 | 19092 | envoy-kafka-broker:9091 |
| envoy-kafka-broker | 9092 | kafka-broker2 | 19092 | envoy-kafka-broker:9092 |
| envoy-kafka-broker | 9093 | kafka-broker3 | 19092 | envoy-kafka-broker:9093 |

{code:bash}
> docker-compose exec kafkacat kafkacat -b envoy-kafka-broker:9091 -L
Metadata for all topics (from broker -1: envoy-kafka-broker:9091/bootstrap):
 3 brokers:
  broker 101 at envoy-kafka-broker:19092
  broker 102 at envoy-kafka-broker:19092 (controller)
  broker 103 at envoy-kafka-broker:19092
 0 topics:
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-13002) dev branch Streams not able to fetch end offsets from pre-3.0 brokers

[John Roesler (Jira)]

John Roesler created KAFKA-13002:


 Summary: dev branch Streams not able to fetch end offsets from 
pre-3.0 brokers
 Key: KAFKA-13002
 URL: https://issues.apache.org/jira/browse/KAFKA-13002
 Project: Kafka
  Issue Type: Bug
  Components: streams
Reporter: John Roesler
 Fix For: 3.0.0
 Attachments: soaks.png

Note: this is not a report against a released version of AK. It seems to be a 
problem on the trunk development branch only.

After deploying our soak test against `trunk/HEAD` on Friday, I noticed that 
Streams is no longer processing:

!soaks.png!

I found this stacktrace in the logs during startup:
{code:java}
5075 [2021-06-25T16:50:44-05:00] 
(streams-soak-trunk-ccloud-alos_soak_i-0691913411e8c77c3_streamslog) 
[2021-06-25 21:50:44,499] WARN [i-0691913411e8c77c3-StreamThread-1] The 
listOffsets request failed. 
(org.apache.kafka.streams.processor.internals.ClientUtils)
 5076 [2021-06-25T16:50:44-05:00] 
(streams-soak-trunk-ccloud-alos_soak_i-0691913411e8c77c3_streamslog) 
java.util.concurrent.ExecutionException: 
org.apache.kafka.common.errors.UnsupportedVersionException: The broker does not 
support LIST_OFFSETS with version in range [7,7].   The supported range is 
[0,6].
 5077 at 
org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
 5078 at 
org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
 5079 at 
org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)
 5080 at 
org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260)
 5081 at 
org.apache.kafka.streams.processor.internals.ClientUtils.getEndOffsets(ClientUtils.java:147)
 5082 at 
org.apache.kafka.streams.processor.internals.StreamsPartitionAssignor.populateClientStatesMap(StreamsPartitionAssignor.java:643)
 5083 at 
org.apache.kafka.streams.processor.internals.StreamsPartitionAssignor.assignTasksToClients(StreamsPartitionAssignor.java:579)
 5084 at 
org.apache.kafka.streams.processor.internals.StreamsPartitionAssignor.assign(StreamsPartitionAssignor.java:387)
 5085 at 
org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:589)
 5086 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:689)
 5087 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:111)
 5088 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:593)
 5089 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:556)
 5090 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1178)
 5091 at 
org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:1153)
 5092 at 
org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:206)
 5093 at 
org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:169)
 5094 at 
org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:129)
 5095 at 
org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:602)
 5096 at 
org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:412)
 5097 at 
org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:297)
 5098 at 
org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:236)
 5099 at 
org.apache.kafka.clients.consumer.KafkaConsumer.pollForFetches(KafkaConsumer.java:1297)
 5100 at 
org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1238)
 5101 at 
org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1211)
 5102 at 
org.apache.kafka.streams.processor.internals.StreamThread.pollRequests(StreamThread.java:932)
 5103 at 
org.apache.kafka.streams.processor.internals.StreamThread.pollPhase(StreamThread.java:885)
 5104 at 
org.apache.kafka.streams.processor.internals.StreamThread.runOnce(StreamThread.java:720)
 5105 at 
org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:583)
 5106 at 
org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:555)
 {code}
Just 

[jira] [Created] (KAFKA-13001) UnitTest Failing

[Srijoni Biswas (Jira)]

Srijoni Biswas created KAFKA-13001:
--

 Summary: UnitTest Failing 
 Key: KAFKA-13001
 URL: https://issues.apache.org/jira/browse/KAFKA-13001
 Project: Kafka
  Issue Type: Test
  Components: unit tests
Affects Versions: 2.7.0
Reporter: Srijoni Biswas


Hi Team, 

Working on kafka repo and the ./gradlew unitTest command is failing in the 2.7 
branch and master branch. The unit test is failing at core:unitTest. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 2.8 #40

[Apache Jenkins Server]

See 

Re: [DISCUSS] KIP-501 Avoid out-of-sync or offline partitions when follower fetch requests are not processed in time

[Satish Duggana]

Hi Mohan,
Please find my inline comments below.

>One small clarification regarding the proposal. I understand how Solution
(1) enables the other replicas to be chosen as the leader. But it is
possible that the other replicas may not be in sync yet and if unclean
leader election is not enabled, the other replicas may not become the
leader right ?

If other replicas are already out of sync for other reasons then
unclean leader election needs to be enabled to choose a leader.
Solution (1) allows the existing insync replicas to be insync even
though the leader takes longer to process their existing fetch
requests.


>It is not clear to me whether Solution 2 can happen independently. For
example, if the leader exceeds *leader.fetch.process.time.max.ms
* due to a transient condition,
should it relinquish leadership immediately ? That might be aggressive in
some cases. Detecting that a leader is slow cannot be determined by just
one occurrence, right ?

Solution(2) is an extension to Solution(1) as mentioned earlier in the
KIP. This config is applicable only if
`follower.fetch.pending.reads.insync.enable` is set as true. I have
also updated the config description in the KIP to make that clear.
In our observations, we do not always see this behavior continuously.
It occurs intermittently and makes all the other requests pile up in
the request queue. Sometimes, the broker goes down and makes the
partitions offline.  Users need to set the config based on their
host's configuration and behavior. We can also think about extending
this config based on others observations.

Thanks,
Satish.

On Mon, 28 Jun 2021 at 04:36, Mohan Parthasarathy  wrote:
>
> Hi Satish,
>
> One small clarification regarding the proposal. I understand how Solution
> (1) enables the other replicas to be chosen as the leader. But it is
> possible that the other replicas may not be in sync yet and if unclean
> leader election is not enabled, the other replicas may not become the
> leader right ?
>
>  It is not clear to me whether Solution 2 can happen independently. For
> example, if the leader exceeds *leader.fetch.process.time.max.ms
> * due to a transient condition,
> should it relinquish leadership immediately ? That might be aggressive in
> some cases. Detecting that a leader is slow cannot be determined by just
> one occurrence, right ?
>
> Thanks
> Mohan
>
>
> On Sun, Jun 27, 2021 at 4:01 AM Satish Duggana 
> wrote:
>
> > Hi Dhruvil,
> > Thanks for looking into the KIP and providing your comments.
> >
> > There are two problems about the scenario raised in this KIP:
> >
> > a) Leader is slow and it is not available for reads or writes.
> > b) Leader is causing the followers to be out of sync and cause the
> > partitions unavailability.
> >
> > (a) should be detected and mitigated so that the broker can become a
> > leader or replace with a different node if this node continues having
> > issues.
> >
> > (b) will cause the partition to go under minimum ISR and eventually
> > make that partition offline if the leader goes down. In this case,
> > users have to enable unclean leader election for making the partition
> > available. This may cause data loss based on the replica chosen as a
> > leader. This is what several folks(including us) observed in their
> > production environments.
> >
> > Solution(1) in the KIP addresses (b) to avoid offline partitions by
> > not removing the replicas from ISR. This allows the partition to be
> > available if the leader is moved to one of the other replicas in ISR.
> >
> > Solution (2) in the KIP extends solution (1) by relinquishing the
> > leadership and allowing one of the other insync replicas to become a
> > leader.
> >
> > ~Satish.
> >

[jira] [Created] (KAFKA-13000) Improve handling of UnsupportedVersionException in MockClient

[Mickael Maison (Jira)]

Mickael Maison created KAFKA-13000:
--

 Summary: Improve handling of UnsupportedVersionException in 
MockClient
 Key: KAFKA-13000
 URL: https://issues.apache.org/jira/browse/KAFKA-13000
 Project: Kafka
  Issue Type: Improvement
Reporter: Mickael Maison


MockClient handles UnsupportedVersionException slightly differently than 
NetworkClient. In some cases, it may throw this exception while instead it 
should return always return a ClientResponse.

Background: https://github.com/apache/kafka/pull/10743#discussion_r655922760



--
This message was sent by Atlassian Jira
(v8.3.4#803005)