[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-tabpanel&focusedCommentId=14133651#comment-14133651 ] gautham varada commented on KAFKA-1633: --- we tried both ack =1 and -1 , same result,

[jira] [Commented] (KAFKA-1025) Producer.send should provide recoverability info on failiure

[ https://issues.apache.org/jira/browse/KAFKA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133944#comment-14133944 ] Jason Rosenberg commented on KAFKA-1025: Yes, I think if the new producer provides

[jira] [Resolved] (KAFKA-1025) Producer.send should provide recoverability info on failiure

[ https://issues.apache.org/jira/browse/KAFKA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein resolved KAFKA-1025. -- Resolution: Won't Fix agreed, I think if there are any exceptions that don't bubble up from the broker

[jira] [Commented] (KAFKA-1611) Improve system test configuration

[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134029#comment-14134029 ] Neha Narkhede commented on KAFKA-1611: -- bq. Once this is committed, I'll add a note a

[jira] [Commented] (KAFKA-1481) Stop using dashes AND underscores as separators in MBean names

[ https://issues.apache.org/jira/browse/KAFKA-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134039#comment-14134039 ] Jun Rao commented on KAFKA-1481: Ok, I am fine with taking this patch as a stop-gap soluti

[jira] [Updated] (KAFKA-1328) Add new consumer APIs

[ https://issues.apache.org/jira/browse/KAFKA-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1328: - Affects Version/s: (was: 0.9.0) 0.8.0 0.8.1 > Ad

[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-tabpanel&focusedCommentId=14134070#comment-14134070 ] Sriharsha Chintalapani commented on KAFKA-1382: --- [~jhooda] Thanks for the in

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

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134184#comment-14134184 ] Joel Koshy commented on KAFKA-1499: --- Yes I will take a look. However, [~omkreddy] can yo

[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 ] Anonymous updated KAFKA-1618: - Status: Patch Available (was: Reopened) > Exception thrown when running console producer with no port num

[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 ] Balaji Seshadri updated KAFKA-1618: --- Attachment: KAFKA-1618-ALL.patch There could be issue in code formatting of my patch.Please le

[jira] [Comment Edited] (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-tabpanel&focusedCommentId=14134322#comment-14134322 ] Balaji Seshadri edited comment on KAFKA-1618 at 9/15/14 6:58 PM: ---

[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: Gwen Shapira) > Exception thrown when running console

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

Re: Review Request 25136: Patch for KAFKA-1610

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25136/#review53391 --- Have talked with Mayuresh and Joel about which mapValues should be c

[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-tabpanel&focusedCommentId=14134437#comment-14134437 ] Krzysztof Szafrański commented on KAFKA-1123: - Sorry, I've been busy lately. I

Re: Review Request 25136: Patch for KAFKA-1610

> On Sept. 15, 2014, 7:49 p.m., Guozhang Wang wrote: > > Have talked with Mayuresh and Joel about which mapValues should be > > converted to map. The summary is that > > > > 1. For now the only place we do in-place modification of a map is in > > ProducePartitionStatus, on isAcksPending and Er

Re: Review Request 25136: Patch for KAFKA-1610

> On Sept. 15, 2014, 7:49 p.m., Guozhang Wang wrote: > > Have talked with Mayuresh and Joel about which mapValues should be > > converted to map. The summary is that > > > > 1. For now the only place we do in-place modification of a map is in > > ProducePartitionStatus, on isAcksPending and Er

[jira] [Assigned] (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 ] Joe Stein reassigned KAFKA-1622: Assignee: Ivan Lyutov > project shouldn't require signing to build > --

[jira] [Assigned] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy reassigned KAFKA-1013: - Assignee: Mayuresh Gharat (was: Tejas Patil) ConsumerOffsetChecker is already done. Mayuresh sai

[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-tabpanel&focusedCommentId=14134699#comment-14134699 ] Sriharsha Chintalapani commented on KAFKA-1558: --- [~junrao] [~nehanarkhede] I

[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-tabpanel&focusedCommentId=14134726#comment-14134726 ] Jagbir commented on KAFKA-1382: --- Hi Sriharsha, Thanks for looking into the issue. We are tr

[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-tabpanel&focusedCommentId=14134742#comment-14134742 ] Jun Rao commented on KAFKA-1558: To simulate a soft failure of a broker, you can 1. kill

[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-tabpanel&focusedCommentId=14134813#comment-14134813 ] Gwen Shapira commented on KAFKA-1618: - I still think that using port 9092 as default m

（info）kafka truncate data of specific topic

Hello kafka I truncate data of kafka as follow 1：stop kafka service 2：delete zookeeper /broker/topics/topic and /consumers/group 3：delete kafka log dir 4：restart kafka service 5：recreate topic info but this way need to stop the service，so how truncate kafka topic data with no stopping kafka serv

[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-tabpanel&focusedCommentId=14134883#comment-14134883 ] Neha Narkhede commented on KAFKA-1618: -- [~gwenshap] The tools that ship with Kafka ar

[jira] [Commented] (KAFKA-1597) New metrics: ResponseQueueSize and BeingSentResponses

[ https://issues.apache.org/jira/browse/KAFKA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134900#comment-14134900 ] Neha Narkhede commented on KAFKA-1597: -- +1. Thanks for the updated patch. > New metr

[jira] [Updated] (KAFKA-1597) New metrics: ResponseQueueSize and BeingSentResponses

[ https://issues.apache.org/jira/browse/KAFKA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1597: - Reviewer: Neha Narkhede > New metrics: ResponseQueueSize and BeingSentResponses >

[jira] [Updated] (KAFKA-1597) New metrics: ResponseQueueSize and BeingSentResponses

[ https://issues.apache.org/jira/browse/KAFKA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1597: - Assignee: Alexis Midon > New metrics: ResponseQueueSize and BeingSentResponses > -

[jira] [Resolved] (KAFKA-1597) New metrics: ResponseQueueSize and BeingSentResponses

[ https://issues.apache.org/jira/browse/KAFKA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-1597. -- Resolution: Fixed Pushed to trunk > New metrics: ResponseQueueSize and BeingSentResponses > ---

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

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134925#comment-14134925 ] Manikumar Reddy commented on KAFKA-1499: [~jjkoshy] I think your are commenting a

Build failed in Jenkins: Kafka-trunk #266

See Changes: [neha.narkhede] KAFKA-1597 New metrics: ResponseQueueSize and BeingSentResponses; reviewed by Neha Narkhede and Jun Rao -- [...truncated 1034 lines...] kafka.integration.PrimitiveApiTes

[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-tabpanel&focusedCommentId=14134947#comment-14134947 ] Jun Rao commented on KAFKA-1282: Nicu, On #2, I wasn't worried about any performance opti

[jira] [Commented] (KAFKA-1507) Using GetOffsetShell against non-existent topic creates the topic unintentionally

[ https://issues.apache.org/jira/browse/KAFKA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134949#comment-14134949 ] Jun Rao commented on KAFKA-1507: Sriharsha, Sorry for the late reply. Since this patch in

[jira] [Commented] (KAFKA-1620) Make kafka api protocol implementation public

[ https://issues.apache.org/jira/browse/KAFKA-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134959#comment-14134959 ] Jun Rao commented on KAFKA-1620: Thanks for the patch. Is there a particular reason that y

[jira] [Commented] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

[ https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134962#comment-14134962 ] Jun Rao commented on KAFKA-1447: Rudolf, Controlled shutdown is designed for rolling boun

[jira] [Commented] (KAFKA-1507) Using GetOffsetShell against non-existent topic creates the topic unintentionally

[ https://issues.apache.org/jira/browse/KAFKA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134964#comment-14134964 ] Sriharsha Chintalapani commented on KAFKA-1507: --- Thanks [~junrao] sounds goo

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

[ https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134925#comment-14134925 ] Manikumar Reddy edited comment on KAFKA-1499 at 9/16/14 5:13 AM: ---

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

Lantao Jin created KAFKA-1635: - Summary: Java doc of makeLeaders in ReplicaManager is wrong Key: KAFKA-1635 URL: https://issues.apache.org/jira/browse/KAFKA-1635 Project: Kafka Issue Type: Bug

[jira] [Updated] (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:all-tabpanel ] Lantao Jin updated KAFKA-1635: -- Attachment: kafka-1635-1.patch > Java doc of makeLeaders in ReplicaManager is wrong > --