Regarding running single core test

Hi, I have tried several times to run same unit test (AdminTest) singly by using command - /./gradlew -Dtest.single=AdminTest core:test/ Only for the first time all the test methods of unit test were executed and later in subsequent runs no test method were executed. Is it a correct

[jira] [Commented] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151423#comment-14151423 ] Anton Karamanov commented on KAFKA-1644: Does this prevent it from being inherited

[jira] [Updated] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-1618: -- Attachment: KAFKA-1618-ALL-VERSION.patch Exception thrown when running console producer with

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151550#comment-14151550 ] BalajiSeshadri commented on KAFKA-1618: --- [~nehanarkhede] and [~junrao],please

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151552#comment-14151552 ] BalajiSeshadri commented on KAFKA-1618: ---

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151663#comment-14151663 ] James Lent commented on KAFKA-1387: --- As background we are using ZooKeeper 3.4.5. When

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151673#comment-14151673 ] James Lent commented on KAFKA-1387: --- In case anyone is interested in the complete code

[jira] [Comment Edited] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151673#comment-14151673 ] James Lent edited comment on KAFKA-1387 at 9/29/14 1:25 PM: In

[jira] [Comment Edited] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151663#comment-14151663 ] James Lent edited comment on KAFKA-1387 at 9/29/14 1:48 PM: As

[jira] [Commented] (KAFKA-899) LeaderNotAvailableException the first time a new message for a partition is processed.

[ https://issues.apache.org/jira/browse/KAFKA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151709#comment-14151709 ] Andras Hatvani commented on KAFKA-899: -- Jun, can I do any support regarding this issue

[jira] [Comment Edited] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151673#comment-14151673 ] James Lent edited comment on KAFKA-1387 at 9/29/14 2:14 PM: In

[jira] [Comment Edited] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151673#comment-14151673 ] James Lent edited comment on KAFKA-1387 at 9/29/14 2:43 PM: In

Re: [DISCUSS] 0.8.2 release branch, unofficial release candidates(s), 0.8.1.2 release

Thanks for making a pass of the open issues, Jun. I agree that it's not worth blocking 0.8.2 more and we can push auto preferred replica election to 0.8.3. I'm a +1 on cutting the branch. On Sun, Sep 28, 2014 at 6:03 PM, Jun Rao jun...@gmail.com wrote: Hi, everyone, I made another pass of the

Re: Review Request 25886: KAFKA-1555: provide strong consistency with reasonable availability

On Sept. 26, 2014, 12:17 a.m., Jun Rao wrote: Thanks for the patch. Looks good overall. A couple of comments. 1. Let's add a check of min.isr in Partition.appendMessagesToLeader() so that the message is not added to the leader's log if isr is less than min.isr. 2. We talked about

[jira] [Commented] (KAFKA-1646) Improve consumer read performance for Windows

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151788#comment-14151788 ] Jay Kreps commented on KAFKA-1646: -- Can you describe the problem in a little more detail?

[jira] [Commented] (KAFKA-1590) Binarize trace level request logging along with debug level text logging

[ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151785#comment-14151785 ] Jay Kreps commented on KAFKA-1590: -- Hmm, I think this is going to be a bit confusing.

Re: [DISCUSS] 0.8.2 release branch, unofficial release candidates(s), 0.8.1.2 release

Agreed, I am +1 on creating the branch. Three thoughts on the branching 1) we should change the version to be 0.8.2.0 (from 0.8.2-SNAPSHOT) on the 0.8.2 branch after the branch is created. 2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever). 3) after we branch I will prepare a

[jira] [Commented] (KAFKA-899) LeaderNotAvailableException the first time a new message for a partition is processed.

[ https://issues.apache.org/jira/browse/KAFKA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151847#comment-14151847 ] Jun Rao commented on KAFKA-899: --- Andras, It seems that your issue is a bit different from

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151873#comment-14151873 ] Jun Rao commented on KAFKA-1387: James, Contributing code to Kafka is pretty simple. You

Re: Review Request 25886: KAFKA-1555: provide strong consistency with reasonable availability

On Sept. 26, 2014, 12:17 a.m., Jun Rao wrote: Thanks for the patch. Looks good overall. A couple of comments. 1. Let's add a check of min.isr in Partition.appendMessagesToLeader() so that the message is not added to the leader's log if isr is less than min.isr. 2. We talked about

Re: Regarding running single core test

This is described in README. Try the following. It will force the test to run when there is no code change. ./gradlew cleanTest test Thanks, Jun On Sun, Sep 28, 2014 at 11:15 PM, Abhishek Sharma abhi.ka...@gmail.com wrote: Hi, I have tried several times to run same unit test (AdminTest)

[jira] [Commented] (KAFKA-899) LeaderNotAvailableException the first time a new message for a partition is processed.

[ https://issues.apache.org/jira/browse/KAFKA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151907#comment-14151907 ] Andras Hatvani commented on KAFKA-899: -- Jun, Jun, Although the reasons may be

[jira] [Comment Edited] (KAFKA-899) LeaderNotAvailableException the first time a new message for a partition is processed.

[ https://issues.apache.org/jira/browse/KAFKA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151907#comment-14151907 ] Andras Hatvani edited comment on KAFKA-899 at 9/29/14 5:23 PM:

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151940#comment-14151940 ] Jun Rao commented on KAFKA-1618: Thanks for the patch. That fixes the compilation issue.

[jira] [Created] (KAFKA-1657) Fetch request using Simple consumer fails due to failed due to Leader not local for partition

aarti gupta created KAFKA-1657: -- Summary: Fetch request using Simple consumer fails due to failed due to Leader not local for partition Key: KAFKA-1657 URL: https://issues.apache.org/jira/browse/KAFKA-1657

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151947#comment-14151947 ] Joel Koshy commented on KAFKA-1499: --- Yes I understand that the LogConfig is at the topic

[jira] [Commented] (KAFKA-1657) Fetch request using Simple consumer fails due to failed due to Leader not local for partition

[ https://issues.apache.org/jira/browse/KAFKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151952#comment-14151952 ] aarti gupta commented on KAFKA-1657: To elaborate on the expected usage. I want to

[jira] [Commented] (KAFKA-1647) Replication offset checkpoints (high water marks) can be lost on hard kills and restarts

[ https://issues.apache.org/jira/browse/KAFKA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151955#comment-14151955 ] Joel Koshy commented on KAFKA-1647: --- Yes that is exactly why it happens and the fix is

[jira] [Created] (KAFKA-1658) Overriding #of partitions per topic, does not take effect

aarti gupta created KAFKA-1658: -- Summary: Overriding #of partitions per topic, does not take effect Key: KAFKA-1658 URL: https://issues.apache.org/jira/browse/KAFKA-1658 Project: Kafka Issue

[jira] [Commented] (KAFKA-899) LeaderNotAvailableException the first time a new message for a partition is processed.

[ https://issues.apache.org/jira/browse/KAFKA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151992#comment-14151992 ] Jun Rao commented on KAFKA-899: --- Andras, If a message couldn't be sent (after all retries),

[jira] [Updated] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-1618: -- Status: Patch Available (was: Reopened) Exception thrown when running console producer with

[jira] [Updated] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-1618: -- Attachment: KAFKA-1618-REUSED-UTILS.patch [~junrao] Please verify Exception thrown when

[jira] [Commented] (KAFKA-1658) Overriding #of partitions per topic, does not take effect

[ https://issues.apache.org/jira/browse/KAFKA-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152016#comment-14152016 ] Sriharsha Chintalapani commented on KAFKA-1658: --- [~aartigupta] In Kafka

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152033#comment-14152033 ] BalajiSeshadri commented on KAFKA-1618: --- [~junrao] Normally core is used by client

Re: [DISCUSS] 0.8.2 release branch, unofficial release candidates(s), 0.8.1.2 release

2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever). I'd vote for changing trunk to 0.8.3-SNAPSHOT. I imagine it will be useful to have 0.8.3 released with some features and bug fixes that we are pushing out of 0.8.2. It will be a while before we get to a point where we can release

[jira] [Updated] (KAFKA-1655) Allow high performance SimpleConsumer use cases to still work with new Kafka 0.9 consumer APIs

[ https://issues.apache.org/jira/browse/KAFKA-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1655: - Reviewer: Neha Narkhede Assignee: (was: Neha Narkhede) Allow high performance

Re: [DISCUSS] 0.8.2 release branch, unofficial release candidates(s), 0.8.1.2 release

+1 on 0.8.3-SNAPSHOT. On 9/29/14 11:40 AM, Neha Narkhede neha.narkh...@gmail.com wrote: 2) change trunk to be 0.9-SNAPSHOT (or 0.8.3-SNAPSHOT or whatever). I'd vote for changing trunk to 0.8.3-SNAPSHOT. I imagine it will be useful to have 0.8.3 released with some features and bug fixes that we

[jira] [Commented] (KAFKA-1634) Update protocol wiki to reflect the new offset management feature

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152044#comment-14152044 ] Neha Narkhede commented on KAFKA-1634: -- Basically, I'm not sure this is great user

[jira] [Updated] (KAFKA-1647) Replication offset checkpoints (high water marks) can be lost on hard kills and restarts

[ https://issues.apache.org/jira/browse/KAFKA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1647: - Affects Version/s: 0.8.2 Replication offset checkpoints (high water marks) can be lost on hard

[jira] [Updated] (KAFKA-1656) replica-assignment option in bin/kakfa-topics.sh doesn't work with alter

[ https://issues.apache.org/jira/browse/KAFKA-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1656: - Labels: newbie (was: ) replica-assignment option in bin/kakfa-topics.sh doesn't work with

Re: Kafka Trunk Branch build failure

HI Jun, The issue kafka-1618 is already open and verified by you/Neha. Thanks, Bhavesh On Sun, Sep 28, 2014 at 3:01 PM, Jun Rao jun...@gmail.com wrote: Bhavesh, The scala 2.9.1 compilation issue seems to be caused by kafka-1618. Reopened that jira. Thanks, Jun On Fri, Sep 26, 2014

[jira] [Comment Edited] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151423#comment-14151423 ] Anton Karamanov edited comment on KAFKA-1644 at 9/29/14 8:49 PM:

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152337#comment-14152337 ] James Lent commented on KAFKA-1387: --- I aplogize in advance for my ignorance, but, I have

[jira] [Updated] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1618: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the latest patch. +1 and

[jira] [Commented] (KAFKA-1499) Broker-side compression configuration

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152354#comment-14152354 ] Jay Kreps commented on KAFKA-1499: -- Hey Joel, that makes sense. I chatted with Neha. I

[jira] [Commented] (KAFKA-1618) Exception thrown when running console producer with no port number for the broker

[ https://issues.apache.org/jira/browse/KAFKA-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152435#comment-14152435 ] BalajiSeshadri commented on KAFKA-1618: --- Thanks a lot [~junrao] Exception thrown

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152453#comment-14152453 ] James Lent commented on KAFKA-1387: --- As for your question (which I agree is one of the

[jira] [Commented] (KAFKA-1634) Update protocol wiki to reflect the new offset management feature

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152466#comment-14152466 ] Joel Koshy commented on KAFKA-1634: --- [~nehanarkhede] I agree that timestamp in the

Build failed in Jenkins: Kafka-trunk #280

See https://builds.apache.org/job/Kafka-trunk/280/changes Changes: [junrao] kafka-1618 (followup); Exception thrown when running console producer with no port number for the broker; patched by Balaji Seshadri; reviewed by Jun Rao -- Started by an SCM

[jira] [Commented] (KAFKA-1494) Failed to send messages after 3 tries.

[ https://issues.apache.org/jira/browse/KAFKA-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152606#comment-14152606 ] Guozhang Wang commented on KAFKA-1494: -- Just to double check, did you make sure the

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152633#comment-14152633 ] Guozhang Wang commented on KAFKA-1305: -- Yeah. Reassigning partitions would take time

[jira] [Updated] (KAFKA-1577) Exception in ConnectionQuotas while shutting down

[ https://issues.apache.org/jira/browse/KAFKA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1577: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk Exception in

Re: jenkins changes required

Jun, can I get access to jenkins http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account to take a stab at fixing trunk? My ldap is joestein. According to INFRA = The gradle plugin is installed - you can invoke gradle build steps with it, Or use the Tool Environment plugin to set a gradle

[jira] [Commented] (KAFKA-1305) Controller can hang on controlled shutdown with auto leader balance enabled

[ https://issues.apache.org/jira/browse/KAFKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152743#comment-14152743 ] Neha Narkhede commented on KAFKA-1305: -- This is a good but potentially very large

Re: jenkins changes required

Joe, I just granted you access to jenkins. Thanks, Jun On Mon, Sep 29, 2014 at 7:34 PM, Joe Stein joe.st...@stealth.ly wrote: Jun, can I get access to jenkins http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account to take a stab at fixing trunk? My ldap is joestein. According to

Build failed in Jenkins: Kafka-trunk #282

See https://builds.apache.org/job/Kafka-trunk/282/ -- Started by user joestein Building remotely on ubuntu3 (Ubuntu ubuntu) in workspace https://builds.apache.org/job/Kafka-trunk/ws/ git rev-parse --is-inside-work-tree Fetching changes from the remote

Build failed in Jenkins: Kafka-trunk #283

See https://builds.apache.org/job/Kafka-trunk/283/ -- Started by user joestein Building remotely on ubuntu3 (Ubuntu ubuntu) in workspace https://builds.apache.org/job/Kafka-trunk/ws/ git rev-parse --is-inside-work-tree Fetching changes from the remote

Jenkins build is back to normal : Kafka-trunk #284

See https://builds.apache.org/job/Kafka-trunk/284/

[jira] [Comment Edited] (KAFKA-1558) AdminUtils.deleteTopic does not work

[ https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152809#comment-14152809 ] Sriharsha Chintalapani edited comment on KAFKA-1558 at 9/30/14 5:23 AM:

[jira] [Commented] (KAFKA-1558) AdminUtils.deleteTopic does not work

[ https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152809#comment-14152809 ] Sriharsha Chintalapani commented on KAFKA-1558: --- [~nehanarkhede] [~junrao]

[jira] [Updated] (KAFKA-1558) AdminUtils.deleteTopic does not work

[ https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-1558: -- Attachment: kafka-thread-dump.log AdminUtils.deleteTopic does not work