[jira] [Commented] (KAFKA-1754) KOYA - Kafka on YARN

[ https://issues.apache.org/jira/browse/KAFKA-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199920#comment-14199920 ] Arun C Murthy commented on KAFKA-1754: -- [~thw] - please feel free to reach out to eit

[jira] [Commented] (KAFKA-1754) KOYA - Kafka on YARN

[ https://issues.apache.org/jira/browse/KAFKA-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199918#comment-14199918 ] Arun C Murthy commented on KAFKA-1754: -- bq. My main concern is whether its possible t

[jira] [Commented] (KAFKA-1754) KOYA - Kafka on YARN

[ https://issues.apache.org/jira/browse/KAFKA-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199917#comment-14199917 ] Arun C Murthy commented on KAFKA-1754: -- Sounds like a great idea, thanks for taking a

[jira] [Comment Edited] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199817#comment-14199817 ] Vishal edited comment on KAFKA-1745 at 11/6/14 5:25 AM: [~junrao]

[jira] [Commented] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199817#comment-14199817 ] Vishal commented on KAFKA-1745: --- [~junrao] Sorry, I should have been more clear. [~ewencp] I

Re: No longer supporting Java 6, if? when?

Mostly converted now to 1.7, this would be welcomed to get any new features. On Wed Nov 05 2014 at 7:32:55 PM Joe Stein wrote: > This has been coming up in a lot of projects and for other reasons too I > wanted to kick off the discussion about if/when we end support for Java 6. > Besides any API

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199702#comment-14199702 ] schandr edited comment on KAFKA-1738 at 11/6/14 3:32 AM: - One more

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199702#comment-14199702 ] schandr commented on KAFKA-1738: One more observance in the server log Here is the Trace

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199678#comment-14199678 ] schandr commented on KAFKA-1738: controller.socket.timeout.ms=9 controller.message.que

[jira] [Commented] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199674#comment-14199674 ] Gwen Shapira commented on KAFKA-1756: - Being able to modify max.message.size without b

[jira] [Commented] (KAFKA-1753) add --decommission-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199675#comment-14199675 ] Joe Stein commented on KAFKA-1753: -- yes > add --decommission-broker option > ---

[jira] [Commented] (KAFKA-1753) add --decommission-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199670#comment-14199670 ] Jun Rao commented on KAFKA-1753: Is the idea just moving all data off the decommissioned t

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199662#comment-14199662 ] Jun Rao commented on KAFKA-1738: What's your value for controller.socket.timeout.ms? > Pa

[jira] [Commented] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199656#comment-14199656 ] Jun Rao commented on KAFKA-1756: I am also wondering if we need to make max.message.bytes

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199643#comment-14199643 ] schandr edited comment on KAFKA-1738 at 11/6/14 2:26 AM: - Thank yo

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199643#comment-14199643 ] schandr commented on KAFKA-1738: Thank you very much for your response. First I think the

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199625#comment-14199625 ] Jun Rao commented on KAFKA-1738: Hmm, that try/catch block is in a while loop. So, the res

[jira] [Commented] (KAFKA-1754) KOYA - Kafka on YARN

[ https://issues.apache.org/jira/browse/KAFKA-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199617#comment-14199617 ] Gwen Shapira commented on KAFKA-1754: - Looking forward to see the patch. Streaming ap

[jira] [Commented] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199616#comment-14199616 ] Joel Koshy commented on KAFKA-1729: --- Incorporated comments. I would actually like to get

[jira] [Updated] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1729: -- Status: Patch Available (was: In Progress) > add doc for Kafka-based offset management in 0.8.2 > -

Re: [Java New Producer] Changing Partition number and its Impact

HI Jay, Thanks for response. I feel this needs to be documented as limitation of New Java Producer Batch size vs buffer size impact when increasing the partition. I agree what you get fine grain control (which is great), but ultimately loosing the functionality of increasing partition for scalabi

[jira] [Updated] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1729: -- Attachment: KAFKA-1782-doc-v2.patch > add doc for Kafka-based offset management in 0.8.2 > -

[jira] [Commented] (KAFKA-1751) handle "broker not exists" scenario

[ https://issues.apache.org/jira/browse/KAFKA-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199600#comment-14199600 ] Jun Rao commented on KAFKA-1751: Could you add a bit more description of what the problem

[jira] [Comment Edited] (KAFKA-1752) add --replace-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199595#comment-14199595 ] Gwen Shapira edited comment on KAFKA-1752 at 11/6/14 1:46 AM: --

[jira] [Commented] (KAFKA-1752) add --replace-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199595#comment-14199595 ] Gwen Shapira commented on KAFKA-1752: - +1 to having this feature. Maybe a more readab

No longer supporting Java 6, if? when?

This has been coming up in a lot of projects and for other reasons too I wanted to kick off the discussion about if/when we end support for Java 6. Besides any API we may want to use in >= 7 we also compile our binaries for 6 for release currently. /*** Joe

[jira] [Commented] (KAFKA-1753) add --decommission-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199564#comment-14199564 ] Joe Stein commented on KAFKA-1753: -- +1 naming the option --decomission-broker > add --de

[jira] [Commented] (KAFKA-1753) add --decommission-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199524#comment-14199524 ] Gwen Shapira commented on KAFKA-1753: - +1 Great idea IMO. Will make life easier for a

[jira] [Commented] (KAFKA-1733) Producer.send will block indeterminately when broker is unavailable.

[ https://issues.apache.org/jira/browse/KAFKA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199508#comment-14199508 ] Jun Rao commented on KAFKA-1733: This is currently marked to be released in 0.8.3. We just

[jira] [Commented] (KAFKA-1684) Implement TLS/SSL authentication

[ https://issues.apache.org/jira/browse/KAFKA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199501#comment-14199501 ] Jun Rao commented on KAFKA-1684: Ivan, Thanks for the patch. Some high level comments. 1

Re: [Java New Producer] Changing Partition number and its Impact

Bhavesh, Wouldn't using the default batch size of 16k have avoided this problem entirely? I think the best solution now is just to change the configuration. What I am saying is it is unlikely you will need to do this again, the problem is just that 1MB partition batches are quite large so you quic

[jira] [Created] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

Joe Stein created KAFKA-1756: Summary: never allow the replica fetch size to be less than the max message size Key: KAFKA-1756 URL: https://issues.apache.org/jira/browse/KAFKA-1756 Project: Kafka

Re: [Java New Producer] Changing Partition number and its Impact

Hi Jay or Kafka Dev Team, Any suggestions, how I can deal with this situation of expanding partitions for New Java Producer for scalability (consumer side) ? Thanks, Bhavesh On Tue, Nov 4, 2014 at 7:08 PM, Bhavesh Mistry wrote: > Also, to added to this Old producer (Scala based in not impact

Re: Review Request 27534: Patch for KAFKA-1746

> On Nov. 5, 2014, 1 a.m., Guozhang Wang wrote: > > Where will testcaseEnv.validationStatusDict["Test completed"] be used? > > Ewen Cheslack-Postava wrote: > That's where all the validation results (the test's assertions) are > stored. It gets scanned through at the end of the test run in

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199132#comment-14199132 ] schandr edited comment on KAFKA-1738 at 11/5/14 9:57 PM: - OkHe

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199132#comment-14199132 ] schandr commented on KAFKA-1738: OkHere is my understanding. This might probably be a

[jira] [Commented] (KAFKA-1684) Implement TLS/SSL authentication

[ https://issues.apache.org/jira/browse/KAFKA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199087#comment-14199087 ] Michael Herstine commented on KAFKA-1684: - Hi Ivan, Thanks-- adding SSL support i

[jira] [Commented] (KAFKA-1752) add --replace-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199032#comment-14199032 ] Dmitry Pekar commented on KAFKA-1752: - Proposal for implementation is following: add -

[jira] [Commented] (KAFKA-1753) add --decommission-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199035#comment-14199035 ] Dmitry Pekar commented on KAFKA-1753: - Proposal for implementation is following: add -

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198894#comment-14198894 ] schandr edited comment on KAFKA-1738 at 11/5/14 7:24 PM: - Please s

[jira] [Updated] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] schandr updated KAFKA-1738: --- Attachment: ServerLogForFailedTopicCreation.txt > Partitions for topic not created after restart from forced s

[jira] [Updated] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] schandr updated KAFKA-1738: --- Attachment: ServerLogForSuccessfulTopicCreation.txt ServerLogForFailedTopicCreation.txt Please

Re: Review Request 27634: Patch for KAFKA-1667

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27634/#review59997 --- I like how you added validations while preserving the API to minimiz

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198829#comment-14198829 ] Dmytro Kostiuchenko commented on KAFKA-1667: Updated reviewboard https://revie

[jira] [Updated] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Kostiuchenko updated KAFKA-1667: --- Attachment: KAFKA-1667_2014-11-05_19:43:53.patch > topic-level configuration not vali

Re: Review Request 27634: Patch for KAFKA-1667

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27634/ --- (Updated Nov. 5, 2014, 6:44 p.m.) Review request for kafka. Bugs: KAFKA-1667

Re: Review Request 27634: Patch for KAFKA-1667

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27634/ --- (Updated Nov. 5, 2014, 6:42 p.m.) Review request for kafka. Bugs: KAFKA-1667

Review Request 27634: Patch for KAFKA-1667

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27634/ --- Review request for kafka. Bugs: KAFKA-1667 https://issues.apache.org/jira/b

[jira] [Commented] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198787#comment-14198787 ] Ewen Cheslack-Postava commented on KAFKA-1745: -- [~junrao] I think he was sayi

[jira] [Updated] (KAFKA-1752) add --replace-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1752: - Reviewer: Neha Narkhede > add --replace-broker option > --- > >

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198747#comment-14198747 ] schandr commented on KAFKA-1738: And I was able to telnet to the host:port. > Partitions

[jira] [Work started] (KAFKA-1752) add --replace-broker option

[ https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1752 started by Dmitry Pekar. --- > add --replace-broker option > --- > > Key

[jira] [Updated] (KAFKA-1751) handle "broker not exists" scenario

[ https://issues.apache.org/jira/browse/KAFKA-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pekar updated KAFKA-1751: Attachment: kafka-1751.patch attached patch > handle "broker not exists" scenario > ---

[jira] [Resolved] (KAFKA-1751) handle "broker not exists" scenario

[ https://issues.apache.org/jira/browse/KAFKA-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pekar resolved KAFKA-1751. - Resolution: Fixed implemented > handle "broker not exists" scenario > ---

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198713#comment-14198713 ] schandr edited comment on KAFKA-1738 at 11/5/14 5:37 PM: - Here are

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198713#comment-14198713 ] schandr commented on KAFKA-1738: Here are the additional logs for the same issue Controll

[jira] [Commented] (KAFKA-391) Producer request and response classes should use maps

[ https://issues.apache.org/jira/browse/KAFKA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198699#comment-14198699 ] Joel Koshy commented on KAFKA-391: -- If there are three partitions, then there will be thre

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198688#comment-14198688 ] Pradeep edited comment on KAFKA-1738 at 11/5/14 5:26 PM: - Can you

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198688#comment-14198688 ] Pradeep commented on KAFKA-1738: Can you provide the configuration files? We are using the

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198678#comment-14198678 ] Jun Rao commented on KAFKA-1738: Yes, I started a kafka broker and ran your script. I was

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198670#comment-14198670 ] Gwen Shapira commented on KAFKA-1667: - I think we can do better validations. For examp

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198663#comment-14198663 ] Gwen Shapira commented on KAFKA-1667: - Can you load the patch to RB too? It makes revi

[jira] [Comment Edited] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198638#comment-14198638 ] Dmytro Kostiuchenko edited comment on KAFKA-1667 at 11/5/14 5:04 PM: ---

[jira] [Comment Edited] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198648#comment-14198648 ] Pradeep edited comment on KAFKA-1738 at 11/5/14 5:03 PM: - I sugges

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198648#comment-14198648 ] Pradeep commented on KAFKA-1738: I suggest you to run the script once on a working setup o

[jira] [Issue Comment Deleted] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Kostiuchenko updated KAFKA-1667: --- Comment: was deleted (was: As suggested on mailing list, moving discussion to JIRA. C

[jira] [Updated] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Kostiuchenko updated KAFKA-1667: --- Attachment: KAFKA-1667.patch Initial patch with 3 TODOs to resolve > topic-level con

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198637#comment-14198637 ] Dmytro Kostiuchenko commented on KAFKA-1667: As suggested on mailing list, mov

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

[ https://issues.apache.org/jira/browse/KAFKA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198633#comment-14198633 ] BalajiSeshadri commented on KAFKA-1476: --- [~junrao] or [~jkreps] Can any of you revi

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198614#comment-14198614 ] Jun Rao commented on KAFKA-1667: If you already started on converting LogConfig to ConfigD

Re: KAFKA-1667 guidance required

Dmytro, We can discuss your questions on the jira. Thanks, Jun On Wed, Nov 5, 2014 at 8:18 AM, Dmytro Kostiuchenko < dmytro.kostiuche...@gmail.com> wrote: > Hi, I decided to fix KAFKA-1667. > > Currently I have an initial patch, which seems to work. I would like > to know, whether overall code

[jira] [Commented] (KAFKA-1738) Partitions for topic not created after restart from forced shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198592#comment-14198592 ] Jun Rao commented on KAFKA-1738: The log shows that the log dir was created for topic_A. W

[jira] [Commented] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198580#comment-14198580 ] Vladimir Tretyakov commented on KAFKA-1723: --- Good news, thx [~junrao] > make th

[jira] [Commented] (KAFKA-1755) Log cleaner thread should not exit on errors

[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198578#comment-14198578 ] Chris Riccomini commented on KAFKA-1755: It might also be desirable to allow the l

KAFKA-1667 guidance required

Hi, I decided to fix KAFKA-1667. Currently I have an initial patch, which seems to work. I would like to know, whether overall code is ok. Also there are few TODOs in the code 1. I haven't added documentation to the properties, as ConfigDef suggests. Should I? 2. I'm not sure what Importance shou

[jira] [Created] (KAFKA-1755) Log cleaner thread should not exit on errors

Joel Koshy created KAFKA-1755: - Summary: Log cleaner thread should not exit on errors Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198537#comment-14198537 ] Jun Rao commented on KAFKA-1745: If you don't call producer.close(), the socket connection

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198533#comment-14198533 ] Jun Rao commented on KAFKA-1667: For now, we can probably just keep LogConfig and add the

[jira] [Commented] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198502#comment-14198502 ] Jun Rao commented on KAFKA-1723: Yes, we can make the mbean names in the new metrics packa

[jira] [Commented] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198439#comment-14198439 ] Vladimir Tretyakov commented on KAFKA-1723: --- Hi [~junrao], {quote} It uses a pr

[jira] [Comment Edited] (KAFKA-1100) metrics shouldn't have generation/timestamp specific names

[ https://issues.apache.org/jira/browse/KAFKA-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198433#comment-14198433 ] Vladimir Tretyakov edited comment on KAFKA-1100 at 11/5/14 2:35 PM:

[jira] [Commented] (KAFKA-1100) metrics shouldn't have generation/timestamp specific names

[ https://issues.apache.org/jira/browse/KAFKA-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198433#comment-14198433 ] Vladimir Tretyakov commented on KAFKA-1100: --- Right [~otis], names will be: {cod

[jira] [Commented] (KAFKA-1667) topic-level configuration not validated

[ https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198212#comment-14198212 ] Dmytro Kostiuchenko commented on KAFKA-1667: Hi. I'm willing to work on this.

[jira] [Updated] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal updated KAFKA-1745: -- Description: Hi, I'm using the java client API for Kafka. I wanted to send data to Kafka by using a produce

[jira] [Updated] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal updated KAFKA-1745: -- Description: Hi, I'm using the java client API for Kafka. I wanted to send data to Kafka by using a produce

[jira] [Comment Edited] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197908#comment-14197908 ] Vishal edited comment on KAFKA-1745 at 11/5/14 8:56 AM: No, since

[jira] [Commented] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197908#comment-14197908 ] Vishal commented on KAFKA-1745: --- No, since I figured that calling producer.close() and retur