[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137011#comment-14137011 ] nicu marasoiu commented on KAFKA-1282: -- Hi, Unfortunately the client used in

[jira] [Comment Edited] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137011#comment-14137011 ] nicu marasoiu edited comment on KAFKA-1282 at 9/17/14 9:53 AM:

[jira] [Updated] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicu marasoiu updated KAFKA-1282: - Attachment: 1282_brushed_up.patch re-attached fixed patch, but we may have a blocker to the whole

[jira] [Updated] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicu marasoiu updated KAFKA-1282: - Attachment: (was: idleDisconnect.patch) Disconnect idle socket connection in Selector

[jira] [Commented] (KAFKA-1635) Java doc of makeLeaders in ReplicaManager is wrong

[ https://issues.apache.org/jira/browse/KAFKA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137044#comment-14137044 ] ASF GitHub Bot commented on KAFKA-1635: --- Github user LantaoJin closed the pull

[GitHub] kafka pull request: KAFKA-1635: Fixed incorrect java doc of makeLe...

Github user LantaoJin closed the pull request at: https://github.com/apache/kafka/pull/33 --- 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

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137118#comment-14137118 ] nicu marasoiu commented on KAFKA-1282: -- here is a time line: he - produced he -

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137130#comment-14137130 ] Nicolae Marasoiu commented on KAFKA-1282: - in fact, this is something that needs

[jira] [Commented] (KAFKA-1633) Data loss if broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137220#comment-14137220 ] gautham varada commented on KAFKA-1633: --- jun, can pl you verify our findings in your

[jira] [Work started] (KAFKA-1622) project shouldn't require signing to build

[ https://issues.apache.org/jira/browse/KAFKA-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1622 started by Ivan Lyutov. -- project shouldn't require signing to build

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137399#comment-14137399 ] Jun Rao commented on KAFKA-1282: Interesting. The data loss may have to do with ack=0,

[jira] [Commented] (KAFKA-1622) project shouldn't require signing to build

[ https://issues.apache.org/jira/browse/KAFKA-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137408#comment-14137408 ] Ivan Lyutov commented on KAFKA-1622: Created reviewboard

[jira] [Commented] (KAFKA-1633) Data loss if broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137405#comment-14137405 ] Jun Rao commented on KAFKA-1633: It sounds like that you killed both brokers at the same

Review Request 25738: Made signing task to execute only when uploadArchives is called

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25738/ --- Review request for kafka. Bugs: KAFKA-1622

[jira] [Updated] (KAFKA-1622) project shouldn't require signing to build

[ https://issues.apache.org/jira/browse/KAFKA-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1622: --- Attachment: KAFKA-1622.patch project shouldn't require signing to build

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137407#comment-14137407 ] Guozhang Wang commented on KAFKA-1461: -- I did not realize this ticket exist, and

[jira] [Updated] (KAFKA-1622) project shouldn't require signing to build

[ https://issues.apache.org/jira/browse/KAFKA-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Lyutov updated KAFKA-1622: --- Status: Patch Available (was: In Progress) project shouldn't require signing to build

[jira] [Resolved] (KAFKA-1629) Replica fetcher thread need to back off upon getting errors on partitions

[ https://issues.apache.org/jira/browse/KAFKA-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1629. -- Resolution: Duplicate Replica fetcher thread need to back off upon getting errors on

Re: kafka 0.8.1: Producer.send() can block forever when a broker is down

Make sense. Please file a JIRA and attach a patch there. It will be great to add a simple test case as well. Thanks, Neha On Wed, Sep 17, 2014 at 8:25 AM, Jonathan Weeks Gmail jonathanbwe...@gmail.com wrote: The issue is that even with one down broker, the rest of the cluster is up, but

[jira] [Commented] (KAFKA-1624) building on JDK 8 fails

[ https://issues.apache.org/jira/browse/KAFKA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137466#comment-14137466 ] Joe Stein commented on KAFKA-1624: -- Thanks, so nothing to fix/to-do yet but lets leave

[jira] [Commented] (KAFKA-1368) Upgrade log4j

[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137492#comment-14137492 ] Abhishek Sharma commented on KAFKA-1368: Log4j 2 is having many advance features

Re: MBeans, dashes, underscores, and KAFKA-1481

Bhavesh, Yes, allowing dot in clientId and topic makes it a bit harder to define the JMX bean names. I see a couple of solutions here. 1. Disable dot in clientId and topic names. The issue is that dot may already be used in existing deployment. 2. We can represent the JMX bean name differently

[jira] [Commented] (KAFKA-1123) Broker IPv6 addresses parsed incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137568#comment-14137568 ] Jun Rao commented on KAFKA-1123: Thanks for the patch. Looks good overall. Some minor

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

Harsha, We are shooting to cut the 0.8.2 branch this month. Thanks, Jun On Tue, Sep 16, 2014 at 11:25 AM, Harsha m...@harsha.io wrote: Hi All, Do we have any ballpark date on the release of 0.8.1.2 or 0.8.2. Thanks, Harsha On Thu, Sep 11, 2014, at 03:53 PM, Jay Kreps wrote: I

[jira] [Commented] (KAFKA-1368) Upgrade log4j

[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137579#comment-14137579 ] Vladislav Pernin commented on KAFKA-1368: - No problem as soon as it is stable (I

Build failed in Jenkins: Kafka-trunk #268

See https://builds.apache.org/job/Kafka-trunk/268/changes Changes: [junrao] kafka-1620; Make kafka api protocol implementation public; patched by Anton Karamanov; reviewed by Jun Rao -- [...truncated 394 lines...] kafka.admin.AdminTest

[jira] [Assigned] (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 ] Balaji Seshadri reassigned KAFKA-1618: -- Assignee: Balaji Seshadri (was: BalajiSeshadri) Exception thrown when running

[jira] [Assigned] (KAFKA-1476) Get a list of consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balaji Seshadri reassigned KAFKA-1476: -- Assignee: Balaji Seshadri (was: BalajiSeshadri) Get a list of consumer groups

[jira] [Assigned] (KAFKA-328) Write unit test for kafka server startup and shutdown API

[ https://issues.apache.org/jira/browse/KAFKA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balaji Seshadri reassigned KAFKA-328: - Assignee: Balaji Seshadri (was: BalajiSeshadri) Write unit test for kafka server

[jira] [Created] (KAFKA-1638) transient unit test failure UncleanLeaderElectionTest

Jun Rao created KAFKA-1638: -- Summary: transient unit test failure UncleanLeaderElectionTest Key: KAFKA-1638 URL: https://issues.apache.org/jira/browse/KAFKA-1638 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-1123) Broker IPv6 addresses parsed incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Szafrański updated KAFKA-1123: Attachment: KAFKA-1123_v3.patch I have updated the patch according to your remarks.

[jira] [Commented] (KAFKA-1639) Support control messages in Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137751#comment-14137751 ] Chris Riccomini commented on KAFKA-1639: One point of discussion is whether the

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137796#comment-14137796 ] nicu marasoiu commented on KAFKA-1282: -- Indeed, ack=1 solves it, it gets a reset by

Re: MBeans, dashes, underscores, and KAFKA-1481

Sure we can do the option 2 for JMX beans. But same solution should be applied to producer.metrics() method for new producer. Regardless of metric is access (JMX or via producer), it has to be consistent naming convention. For example, I get following metric name when my topic is topic.dot. So

[Java New Producer] CPU Usage Spike to 100% when network connection is lost

Hi Kafka Dev team, I see my CPU spike to 100% when network connection is lost for while. It seems network IO thread are very busy logging following error message. Is this expected behavior ? 2014-09-17 14:06:16.830 [kafka-producer-network-thread] ERROR

Re: MBeans, dashes, underscores, and KAFKA-1481

Hi Jun, On Wed, Sep 17, 2014 at 12:35 PM, Jun Rao jun...@gmail.com wrote: Bhavesh, Yes, allowing dot in clientId and topic makes it a bit harder to define the JMX bean names. I see a couple of solutions here. 1. Disable dot in clientId and topic names. The issue is that dot may already be

[jira] [Commented] (KAFKA-1382) Update zkVersion on partition state update failures

[ https://issues.apache.org/jira/browse/KAFKA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138191#comment-14138191 ] Noah Yetter commented on KAFKA-1382: We put a decent amount of effort at replicating

[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=14138359#comment-14138359 ] Neha Narkhede commented on KAFKA-1618: -- Agree with [~gwenshap] that whichever way we

[jira] [Updated] (KAFKA-1638) transient unit test failure UncleanLeaderElectionTest

[ https://issues.apache.org/jira/browse/KAFKA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1638: - Labels: newbie++ (was: ) transient unit test failure UncleanLeaderElectionTest

Re: [Java New Producer] CPU Usage Spike to 100% when network connection is lost

This seems like a problem. Please can you file a JIRA and attach the log4j output there? On Wed, Sep 17, 2014 at 2:14 PM, Bhavesh Mistry mistry.p.bhav...@gmail.com wrote: Hi Kafka Dev team, I see my CPU spike to 100% when network connection is lost for while. It seems network IO thread are

[jira] [Comment Edited] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137796#comment-14137796 ] nicu marasoiu edited comment on KAFKA-1282 at 9/18/14 5:12 AM:

[jira] [Comment Edited] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137796#comment-14137796 ] nicu marasoiu edited comment on KAFKA-1282 at 9/18/14 5:21 AM:

[jira] [Comment Edited] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137796#comment-14137796 ] nicu marasoiu edited comment on KAFKA-1282 at 9/18/14 5:25 AM: