Re: Review Request 34766: Patch for KAFKA-2229

[Andrii Biletskyi]

> On Сер. 14, 2015, 3:48 до полудня, Grant Henke wrote:
> > core/src/main/scala/kafka/server/TopicCommandHelper.scala, lines 146-153
> > 
> >
> > This logic is fairly complex and difficult to track. I am not sure the 
> > best way to resolve it. Breaking it into smaller functions may help.

I agree it's hard to follow this logic, it's true the algorithm itself is 
complicated. Details and suggestions how exactly we can make this part clearer 
could be helpful here.


- Andrii


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34766/#review95376
---


On Червень 30, 2015, 1:59 після полудня, Andrii Biletskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/34766/
> ---
> 
> (Updated Червень 30, 2015, 1:59 після полудня)
> 
> 
> Review request for kafka.
> 
> 
> Bugs: KAFKA-2229
> https://issues.apache.org/jira/browse/KAFKA-2229
> 
> 
> Repository: kafka
> 
> 
> Description
> ---
> 
> KIP-4 Phase 1 Rebase
> 
> 
> Diffs
> -
> 
>   checkstyle/import-control.xml f2e6cec267e67ce8e261341e373718e14a8e8e03 
>   clients/src/main/java/org/apache/kafka/common/ConfigEntry.java PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/PartitionReplicaAssignment.java 
> PRE-CREATION 
>   clients/src/main/java/org/apache/kafka/common/TopicConfigInfo.java 
> PRE-CREATION 
>   clients/src/main/java/org/apache/kafka/common/protocol/ApiKeys.java 
> b39e9bb53dd51f1ce931691e23aabc9ebaebf1e7 
>   clients/src/main/java/org/apache/kafka/common/protocol/Errors.java 
> 5b898c8f8ad5d0469f469b600c4b2eb13d1fc662 
>   clients/src/main/java/org/apache/kafka/common/protocol/Protocol.java 
> 3dc8b015afd2347a41c9a9dbc02b8e367da5f75f 
>   clients/src/main/java/org/apache/kafka/common/requests/AbstractRequest.java 
> 5d3d52859587ce0981d702f04042b0f6e1bc3704 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/AlterTopicRequest.java
>  PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/AlterTopicResponse.java
>  PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/CreateTopicRequest.java
>  PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/CreateTopicResponse.java
>  PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/DeleteTopicRequest.java
>  PRE-CREATION 
>   
> clients/src/main/java/org/apache/kafka/common/requests/admin/DeleteTopicResponse.java
>  PRE-CREATION 
>   
> clients/src/test/java/org/apache/kafka/common/requests/RequestResponseTest.java
>  8b2aca85fa738180e5420985fddc39a4bf9681ea 
>   core/src/main/scala/kafka/admin/AdminUtils.scala 
> f06edf41c732a7b794e496d0048b0ce6f897e72b 
>   core/src/main/scala/kafka/api/RequestKeys.scala 
> 155cb650e9cffe2c950326cfc25b1480cda819db 
>   core/src/main/scala/kafka/common/InvalidPartitionsException.scala 
> PRE-CREATION 
>   core/src/main/scala/kafka/common/InvalidReplicaAssignmentException.scala 
> PRE-CREATION 
>   core/src/main/scala/kafka/common/InvalidReplicationFactorException.scala 
> PRE-CREATION 
>   core/src/main/scala/kafka/common/InvalidTopicConfigurationException.scala 
> PRE-CREATION 
>   
> core/src/main/scala/kafka/common/ReassignPartitionsInProgressException.scala 
> PRE-CREATION 
>   core/src/main/scala/kafka/server/KafkaApis.scala 
> ad6f05807c61c971e5e60d24bc0c87e989115961 
>   core/src/main/scala/kafka/server/TopicCommandHelper.scala PRE-CREATION 
>   core/src/test/scala/unit/kafka/admin/AdminTest.scala 
> 252ac813c8df1780c2dc5fa9e698fb43bb6d5cf8 
>   core/src/test/scala/unit/kafka/server/TopicCommandHelperTest.scala 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/34766/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrii Biletskyi
> 
>

[jira] [Commented] (KAFKA-2229) Phase 1: Requests and KafkaApis

[Andrii Biletskyi (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742109#comment-14742109
 ] 

Andrii Biletskyi commented on KAFKA-2229:
-

Sorry I was on vacation so didn't have time to work on this issue. I think I 
resolved all your comments now I need to rebase changes to the trunk and commit 
corresponding fixes per your comments. It's been a while since last rebase, but 
still I think it will be quicker if I do it.
Your help will be very appreciated in reviewing again after rebase. As I can 
see there were some changes in replica assignment code which my changes use a 
lot, this part is pretty critical. Also you could provide more details (or even 
recommendations) to your comment 
"This logic is fairly complex and difficult to track. I am not sure the best 
way to resolve it. Breaking it into smaller functions may help."
-> I've updated on it in RB.

Thanks, 
Andrii

> Phase 1: Requests and KafkaApis
> ---
>
> Key: KAFKA-2229
> URL: https://issues.apache.org/jira/browse/KAFKA-2229
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Andrii Biletskyi
>Assignee: Andrii Biletskyi
> Attachments: KAFKA-2229.patch, KAFKA-2229_2015-06-30_16:59:17.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-2229) Phase 1: Requests and KafkaApis

[Andrii Biletskyi (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742108#comment-14742108
 ] 

Andrii Biletskyi commented on KAFKA-2229:
-

Sorry I was on vacation so didn't have time to work on this issue. I think I 
resolved all your comments now I need to rebase changes to the trunk and commit 
corresponding fixes per your comments. It's been a while since last rebase, but 
still I think it will be quicker if I do it.
Your help will be very appreciated in reviewing again after rebase. As I can 
see there were some changes in replica assignment code which my changes use a 
lot, this part is pretty critical. Also you could provide more details (or even 
recommendations) to your comment 
"This logic is fairly complex and difficult to track. I am not sure the best 
way to resolve it. Breaking it into smaller functions may help."
-> I've updated on it in RB.

Thanks, 
Andrii

> Phase 1: Requests and KafkaApis
> ---
>
> Key: KAFKA-2229
> URL: https://issues.apache.org/jira/browse/KAFKA-2229
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Andrii Biletskyi
>Assignee: Andrii Biletskyi
> Attachments: KAFKA-2229.patch, KAFKA-2229_2015-06-30_16:59:17.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Maybe 0.8.3 should really be 0.9.0?

[Jun Rao]

It seems that everyone is in favor of renaming 0.8.3 to 0.9.0. I made the
following changes in the jira: (1) rename version 0.9.0 to 0.10.0.0; (2)
rename version 0.8.3 to 0.9.0.0; (3) add version 0.9.0.1.

Thanks,

Jun

On Thu, Sep 10, 2015 at 10:08 AM, Joe Stein  wrote:

> Jun,
>
> Makes sense, thanks!
>
> ~ Joestein
> On Sep 10, 2015 1:05 PM, "Jun Rao"  wrote:
>
> > Hi, Joe,
> >
> > One of the reasons that we have been doing beta releases before is to
> > stabilize the public apis. However, in trunk, we have introduced the api
> > stability annotation. The new java consumer api is marked as unstable.
> With
> > this, even if we name the first release of the new consumer as 0.9.0.0
> > (i.e., w/o beta), the users will understand that the api is subject to
> > change. Then, we just need to be prepared for 0.9.0.x releases soon after
> > for critical bug fixes since there are lots of new code in 0.9.0.0.
> >
> > Thanks,
> >
> > Jun
> >
> > On Thu, Sep 10, 2015 at 8:24 AM, Joe Stein  wrote:
> >
> > > are we going to deem the new consumer in 0.9.0 as beta? Do we want
> to-do
> > a
> > > 0.9.0-beta and this way when the consumer is g2g we 0.9.0.0
> > >
> > > 0.9.0-beta also allows us to release a lot of new things a bit sooner
> and
> > > have some good cycles of fixes (because you know they will come)
> > >
> > > There is enough new stuff that 0.9-something makes sense, +1 on not
> 0.8.3
> > >
> > >
> > > On Thu, Sep 10, 2015 at 11:01 AM, Grant Henke 
> > wrote:
> > >
> > > > +1 for 0.9
> > > >
> > > > On Wed, Sep 9, 2015 at 2:20 AM, Stevo Slavić 
> > wrote:
> > > >
> > > > > +1 (non-binding) for 0.9
> > > > >
> > > > > On Wed, Sep 9, 2015 at 6:41 AM, Jun Rao  wrote:
> > > > >
> > > > > > +1 for 0.9.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Jun
> > > > > >
> > > > > > On Tue, Sep 8, 2015 at 3:04 PM, Ismael Juma 
> > > wrote:
> > > > > >
> > > > > > > +1 (non-binding) for 0.9.
> > > > > > >
> > > > > > > Ismael
> > > > > > >
> > > > > > > On Tue, Sep 8, 2015 at 10:19 AM, Gwen Shapira <
> g...@confluent.io
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi Kafka Fans,
> > > > > > > >
> > > > > > > > What do you think of making the next release (the one with
> > > > security,
> > > > > > new
> > > > > > > > consumer, quotas, etc) a 0.9.0 instead of 0.8.3?
> > > > > > > >
> > > > > > > > It has lots of new features, and new consumer was pretty much
> > > > scoped
> > > > > > for
> > > > > > > > 0.9.0, so it matches our original roadmap. I feel that so
> many
> > > > > awesome
> > > > > > > > features deserve a better release number.
> > > > > > > >
> > > > > > > > The downside is mainly some confusion (we refer to 0.8.3 in
> > bunch
> > > > of
> > > > > > > > places), and noisy emails from JIRA while we change "fix
> > version"
> > > > > field
> > > > > > > > everywhere.
> > > > > > > >
> > > > > > > > Thoughts?
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Grant Henke
> > > > Software Engineer | Cloudera
> > > > gr...@cloudera.com | twitter.com/gchenke |
> linkedin.com/in/granthenke
> > > >
> > >
> >
>

0.9.0.0 remaining jiras

[Jun Rao]

The following is a candidate list of jiras that we want to complete in the
upcoming release (0.9.0.0). Our goal is to finish at least all the blockers
and as many as the non-blockers possible in that list.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.9.0.0

Anything should be added/removed from this list?

We are shooting to cut an 0.9.0.0 release branch in early October.

Thanks,

Jun

Re: 0.9.0.0 remaining jiras

[Edward Ribeiro]

Excuse me, I'd put my issue in this list on the backburner, but resuming
work on it this week.

Cheers,
Eddie
Em 12/09/2015 13:40, "Jun Rao"  escreveu:

> The following is a candidate list of jiras that we want to complete in the
> upcoming release (0.9.0.0). Our goal is to finish at least all the blockers
> and as many as the non-blockers possible in that list.
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.9.0.0
>
> Anything should be added/removed from this list?
>
> We are shooting to cut an 0.9.0.0 release branch in early October.
>
> Thanks,
>
> Jun
>

[jira] [Assigned] (KAFKA-2504) Stop logging WARN when client disconnects

[Jeff Holoman (JIRA)]

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

Jeff Holoman reassigned KAFKA-2504:
---

Assignee: Jeff Holoman

> Stop logging WARN when client disconnects
> -
>
> Key: KAFKA-2504
> URL: https://issues.apache.org/jira/browse/KAFKA-2504
> Project: Kafka
>  Issue Type: Bug
>Reporter: Gwen Shapira
>Assignee: Jeff Holoman
> Fix For: 0.9.0.0
>
>
> I thought we fixed this one, but it came back. This can be fill logs and is 
> fairly useless. Should be logged at DEBUG level:
> {code}
> [2015-09-02 12:05:59,743] WARN Error in I/O with connection to /10.191.0.36 
> (org.apache.kafka.common.network.Selector)
> java.io.IOException: Connection reset by peer
>   at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
>   at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
>   at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
>   at sun.nio.ch.IOUtil.read(IOUtil.java:197)
>   at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
>   at 
> org.apache.kafka.common.network.PlaintextTransportLayer.read(PlaintextTransportLayer.java:111)
>   at 
> org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:81)
>   at 
> org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:71)
>   at 
> org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:154)
>   at 
> org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:135)
>   at org.apache.kafka.common.network.Selector.poll(Selector.java:296)
>   at kafka.network.Processor.run(SocketServer.scala:405)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KAFKA-2539) Double semi-colon in import statement

[Alex Shoei (JIRA)]

Alex Shoei created KAFKA-2539:
-

 Summary: Double semi-colon in import statement
 Key: KAFKA-2539
 URL: https://issues.apache.org/jira/browse/KAFKA-2539
 Project: Kafka
  Issue Type: Bug
  Components: clients
Reporter: Alex Shoei


LeaderAndIsrResponse contains double semi in import. Line 23



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KAFKA-2539) Double semi-colon in import statement

[Alex Shoei (JIRA)]

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

Alex Shoei resolved KAFKA-2539.
---
Resolution: Not A Problem

> Double semi-colon in import statement
> -
>
> Key: KAFKA-2539
> URL: https://issues.apache.org/jira/browse/KAFKA-2539
> Project: Kafka
>  Issue Type: Bug
>  Components: clients
>Reporter: Alex Shoei
>
> LeaderAndIsrResponse contains double semi in import. Line 23



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KAFKA-2540) Inconsistent constant pertaining to autoCommitEnable

[Muthu Jayakumar (JIRA)]

Muthu Jayakumar created KAFKA-2540:
--

 Summary: Inconsistent constant pertaining to autoCommitEnable
 Key: KAFKA-2540
 URL: https://issues.apache.org/jira/browse/KAFKA-2540
 Project: Kafka
  Issue Type: Bug
  Components: clients, consumer
Affects Versions: 0.8.2.1
Reporter: Muthu Jayakumar
Assignee: Neha Narkhede
Priority: Minor


Hello there,

It seems like the class kafka.consumer.ConsumerConfig containing
{quote}
val autoCommitEnable = props.getBoolean("auto.commit.enable", AutoCommit)
{quote}
is inconsistent with org.apache.kafka.clients.consumer.ConsumerConfig
{quote}
public static final String ENABLE_AUTO_COMMIT_CONFIG = "enable.auto.commit";
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] kafka pull request: KAFKA-2538: Fixing a compilation error in trun...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/208


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (KAFKA-2538) Compilation in trunk is failing due to https://github.com/apache/kafka/commit/845514d62329be8382e6d02b8041fc858718d534

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742341#comment-14742341
 ] 

ASF GitHub Bot commented on KAFKA-2538:
---

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/208


> Compilation in trunk is failing due to 
> https://github.com/apache/kafka/commit/845514d62329be8382e6d02b8041fc858718d534
> --
>
> Key: KAFKA-2538
> URL: https://issues.apache.org/jira/browse/KAFKA-2538
> Project: Kafka
>  Issue Type: Bug
>Reporter: Parth Brahmbhatt
>Assignee: Parth Brahmbhatt
>Priority: Blocker
>
> Getting 
> /Users/pbrahmbhatt/repo/kafka/core/src/main/scala/kafka/tools/EndToEndLatency.scala:82:
>  value commit is not a member of 
> org.apache.kafka.clients.consumer.KafkaConsumer[Array[Byte],Array[Byte]]
>   consumer.commit(CommitType.SYNC)
>^
> Which I believe was missed when committing KAFKA-2389 which replaces all 
> occurrences of commit(mode) with commit(Sync/Async). This is resulting in 
> other PRS reporting as bad by jenkins like 
> https://github.com/apache/kafka/pull/195 where 2 failures were reported by 
> jenkins https://builds.apache.org/job/kafka-trunk-git-pr/410/ and 
> https://builds.apache.org/job/kafka-trunk-git-pr/411/ 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KAFKA-2538) Compilation in trunk is failing due to https://github.com/apache/kafka/commit/845514d62329be8382e6d02b8041fc858718d534

[Guozhang Wang (JIRA)]

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

Guozhang Wang resolved KAFKA-2538.
--
   Resolution: Fixed
Fix Version/s: 0.9.0.0

> Compilation in trunk is failing due to 
> https://github.com/apache/kafka/commit/845514d62329be8382e6d02b8041fc858718d534
> --
>
> Key: KAFKA-2538
> URL: https://issues.apache.org/jira/browse/KAFKA-2538
> Project: Kafka
>  Issue Type: Bug
>Reporter: Parth Brahmbhatt
>Assignee: Parth Brahmbhatt
>Priority: Blocker
> Fix For: 0.9.0.0
>
>
> Getting 
> /Users/pbrahmbhatt/repo/kafka/core/src/main/scala/kafka/tools/EndToEndLatency.scala:82:
>  value commit is not a member of 
> org.apache.kafka.clients.consumer.KafkaConsumer[Array[Byte],Array[Byte]]
>   consumer.commit(CommitType.SYNC)
>^
> Which I believe was missed when committing KAFKA-2389 which replaces all 
> occurrences of commit(mode) with commit(Sync/Async). This is resulting in 
> other PRS reporting as bad by jenkins like 
> https://github.com/apache/kafka/pull/195 where 2 failures were reported by 
> jenkins https://builds.apache.org/job/kafka-trunk-git-pr/410/ and 
> https://builds.apache.org/job/kafka-trunk-git-pr/411/ 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: Kafka-trunk #621

[Apache Jenkins Server]

See 

Changes:

[wangguoz] KAFKA-2538: Fixing a compilation error in trunk.

--
[...truncated 845 lines...]
kafka.coordinator.ConsumerCoordinatorResponseTest > 
testJoinGroupUnknownPartitionAssignmentStrategy PASSED

kafka.coordinator.ConsumerCoordinatorResponseTest > 
testJoinGroupInconsistentPartitionAssignmentStrategy PASSED

kafka.coordinator.ConsumerCoordinatorResponseTest > 
testJoinGroupUnknownConsumerNewGroup PASSED

kafka.coordinator.ConsumerCoordinatorResponseTest > testValidJoinGroup PASSED

kafka.api.QuotasTest > testProducerConsumerOverrideUnthrottled PASSED

kafka.coordinator.ConsumerCoordinatorResponseTest > 
testHeartbeatUnknownConsumerExistingGroup PASSED

kafka.coordinator.ConsumerCoordinatorResponseTest > testValidHeartbeat PASSED

kafka.api.ProducerSendTest > testCloseWithZeroTimeoutFromCallerThread PASSED

kafka.admin.AdminTest > testResumePartitionReassignmentThatWasCompleted PASSED

kafka.integration.SslTopicMetadataTest > 
testAliveBrokersListWithNoTopicsAfterNewBrokerStartup PASSED

kafka.admin.AdminTest > testManualReplicaAssignment PASSED

kafka.admin.DeleteConsumerGroupTest > 
testGroupTopicWideDeleteInZKForGroupConsumingMultipleTopics PASSED

kafka.integration.SslTopicMetadataTest > testBasicTopicMetadata PASSED

kafka.integration.PrimitiveApiTest > testMultiProduce PASSED

kafka.admin.DeleteTopicTest > testResumeDeleteTopicWithRecoveredFollower PASSED

kafka.admin.AddPartitionsTest > testManualAssignmentOfReplicas PASSED

kafka.integration.SslTopicMetadataTest > testTopicMetadataRequest PASSED

kafka.integration.PrimitiveApiTest > testDefaultEncoderProducerAndFetch PASSED

kafka.api.ConsumerTest > testPositionAndCommit PASSED

kafka.admin.AdminTest > testPartitionReassignmentWithLeaderInNewReplicas PASSED

kafka.admin.DeleteConsumerGroupTest > testGroupWideDeleteInZK PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicAlreadyMarkedAsDeleted PASSED

kafka.integration.PrimitiveApiTest > testFetchRequestCanProperlySerialize PASSED

kafka.integration.FetcherTest > testFetcher PASSED

kafka.zk.ZKEphemeralTest > testEphemeralNodeCleanup PASSED

kafka.api.ProducerSendTest > testCloseWithZeroTimeoutFromSenderThread PASSED

kafka.utils.UtilsTest > testAbs PASSED

kafka.utils.UtilsTest > testReplaceSuffix PASSED

kafka.utils.UtilsTest > testDoublyLinkedList PASSED

kafka.utils.UtilsTest > testCircularIterator PASSED

kafka.utils.UtilsTest > testReadBytes PASSED

kafka.utils.UtilsTest > testCsvList PASSED

kafka.utils.UtilsTest > testReadInt PASSED

kafka.utils.UtilsTest > testCsvMap PASSED

kafka.utils.UtilsTest > testInLock PASSED

kafka.utils.UtilsTest > testSwallow PASSED

kafka.integration.SslTopicMetadataTest > 
testAliveBrokersListWithNoTopicsAfterABrokerShutdown PASSED

kafka.integration.PrimitiveApiTest > testPipelinedProduceRequests PASSED

kafka.api.ConsumerTest > testUnsubscribeTopic PASSED

kafka.log.LogCleanerIntegrationTest > cleanerTest[0] PASSED

kafka.admin.AdminTest > testShutdownBroker PASSED

kafka.admin.AdminTest > testTopicCreationWithCollision PASSED

kafka.admin.AddPartitionsTest > testReplicaPlacement PASSED

kafka.api.QuotasTest > testThrottledProducerConsumer PASSED

kafka.utils.JsonTest > testJsonEncoding PASSED

kafka.admin.AdminTest > testTopicCreationInZK PASSED

kafka.admin.DeleteTopicTest > testPartitionReassignmentDuringDeleteTopic PASSED

kafka.integration.PrimitiveApiTest > testProduceAndMultiFetch PASSED

kafka.integration.PrimitiveApiTest > 
testDefaultEncoderProducerAndFetchWithCompression PASSED

kafka.api.ConsumerTest > testListTopics PASSED

kafka.admin.DeleteTopicTest > testDeleteNonExistingTopic PASSED

kafka.integration.PrimitiveApiTest > testConsumerEmptyTopic PASSED

kafka.integration.PlaintextTopicMetadataTest > 
testIsrAfterBrokerShutDownAndJoinsBack PASSED

kafka.integration.PrimitiveApiTest > testEmptyFetchRequest PASSED

kafka.integration.PlaintextTopicMetadataTest > testAutoCreateTopicWithCollision 
PASSED

kafka.api.ConsumerTest > testExpandingTopicSubscriptions PASSED

kafka.admin.DeleteTopicTest > testRecreateTopicAfterDeletion PASSED

kafka.integration.UncleanLeaderElectionTest > testUncleanLeaderElectionEnabled 
PASSED

kafka.api.ConsumerBounceTest > testConsumptionWithBrokerFailures PASSED

kafka.utils.CommandLineUtilsTest > testParseEmptyArg PASSED

kafka.utils.CommandLineUtilsTest > testParseSingleArg PASSED

kafka.utils.CommandLineUtilsTest > testParseArgs PASSED

kafka.integration.PlaintextTopicMetadataTest > testAliveBrokerListWithNoTopics 
PASSED

kafka.integration.PlaintextTopicMetadataTest > testAutoCreateTopic PASSED

kafka.integration.PlaintextTopicMetadataTest > testGetAllTopicMetadata PASSED

kafka.admin.DeleteTopicTest > testAddPartitionDuringDeleteTopic PASSED

kafka.api.ConsumerTest > testPatternUnsubscription PASSED

kafka.integration.PlaintextTopicMetadataTest > 
testAliveBrokersListWithNoTopicsAfterNewBrokerStartup P