Re: Review Request 30763: Second attempt at flush()

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30763/#review73475 --- clients/src/main/java/org/apache/kafka/clients/producer/KafkaProduc

[jira] [Commented] (KAFKA-1788) producer record can stay in RecordAccumulator forever if leader is no available

[ https://issues.apache.org/jira/browse/KAFKA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333041#comment-14333041 ] Ewen Cheslack-Postava commented on KAFKA-1788: -- Ok, I'll try to clear up a fe

Re: Review Request 29379: Patch for KAFKA-1788

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29379/#review73512 --- Minor comments, I think the biggest issue remaining is getting Send

Re: Review Request 29379: Patch for KAFKA-1788

> On Jan. 6, 2015, 6:43 p.m., Parth Brahmbhatt wrote: > > clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java, > > line 225 > > > > > > sender.completeBatch() is only called as par

[jira] [Commented] (KAFKA-1969) NPE in unit test for new consumer

[ https://issues.apache.org/jira/browse/KAFKA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333034#comment-14333034 ] Guozhang Wang commented on KAFKA-1969: -- Thanks Jay. I am working on some of those iss

[jira] [Commented] (KAFKA-1680) JmxTool exits if no arguments are given

[ https://issues.apache.org/jira/browse/KAFKA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333020#comment-14333020 ] Ewen Cheslack-Postava commented on KAFKA-1680: -- Pretty sure this is still a b

[jira] [Commented] (KAFKA-1971) starting a broker with a conflicting id will delete the previous broker registration

[ https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333015#comment-14333015 ] Jun Rao commented on KAFKA-1971: It seems that the reason why we explicitly delete the bro

[jira] [Commented] (KAFKA-1971) starting a broker with a conflicting id will delete the previous broker registration

[ https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333012#comment-14333012 ] Jun Rao commented on KAFKA-1971: Updated reviewboard https://reviews.apache.org/r/31260/di

Re: Review Request 31260: Patch for kafka-1971

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31260/ --- (Updated Feb. 23, 2015, 5:11 a.m.) Review request for kafka. Bugs: kafka-1971

[jira] [Updated] (KAFKA-1971) starting a broker with a conflicting id will delete the previous broker registration

[ https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1971: --- Attachment: kafka-1971_2015-02-22_21:11:52.patch > starting a broker with a conflicting id will delete the pre

Re: Review Request 30763: Second attempt at flush()

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30763/#review73505 --- Ship it! Thanks Jay. Looks good to me. Just a minor comment. clie

[jira] [Commented] (KAFKA-1976) transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown

[ https://issues.apache.org/jira/browse/KAFKA-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332515#comment-14332515 ] Gwen Shapira commented on KAFKA-1976: - Thanks [~harsha_ch]. As I mentioned in KAFKA-1

[jira] [Commented] (KAFKA-1976) transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown

[ https://issues.apache.org/jira/browse/KAFKA-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332514#comment-14332514 ] Sriharsha Chintalapani commented on KAFKA-1976: --- [~junrao] I covered this is

[jira] [Commented] (KAFKA-1976) transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown

[ https://issues.apache.org/jira/browse/KAFKA-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332513#comment-14332513 ] Jun Rao commented on KAFKA-1976: I suspect the issue is the following: Since broker failur

[jira] [Created] (KAFKA-1976) transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown

Jun Rao created KAFKA-1976: -- Summary: transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown Key: KAFKA-1976 URL: https://issues.apache.org/jira/browse/KAFKA-1976

[jira] [Commented] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332503#comment-14332503 ] jaikiran pai commented on KAFKA-1907: - Hi [~nehanarkhede], I submitted a patch for thi

[jira] [Updated] (KAFKA-724) Allow automatic socket.send.buffer from operating system

[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-724: -- Reviewer: Jay Kreps Affects Version/s: 0.8.2.0 Status: Patch Available (was:

[jira] [Commented] (KAFKA-724) Allow automatic socket.send.buffer from operating system

[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332482#comment-14332482 ] ASF GitHub Bot commented on KAFKA-724: -- GitHub user rekhajoshm opened a pull request:

[GitHub] kafka pull request: KAFKA-724: auto socket buffer set

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/50 KAFKA-724: auto socket buffer set KAFKA-724: Allow automatic socket.send.buffer from operating system If socket.receive.buffer.bytes/socket.send.buffer.bytes set to non-zero/-1, the OS default

[jira] [Updated] (KAFKA-269) ./system_test/producer_perf/bin/run-test.sh without --async flag does not run

[ https://issues.apache.org/jira/browse/KAFKA-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-269: -- Reviewer: Jay Kreps Affects Version/s: 0.8.1.1 Status: Patch Available (was:

[jira] [Commented] (KAFKA-269) ./system_test/producer_perf/bin/run-test.sh without --async flag does not run

[ https://issues.apache.org/jira/browse/KAFKA-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332475#comment-14332475 ] ASF GitHub Bot commented on KAFKA-269: -- GitHub user rekhajoshm opened a pull request:

[GitHub] kafka pull request: KAFKA-269: run-test.sh async test

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/49 KAFKA-269: run-test.sh async test KAFKA-269: run-test.sh async test You can merge this pull request into a Git repository by running: $ git pull https://github.com/rekhajoshm/kafka KAFKA-269

[jira] [Commented] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332459#comment-14332459 ] Guozhang Wang commented on KAFKA-1865: -- Does it hang on ConsumerTest? Maybe we can di

Re: How to get a JIRA assigned

Anyone know if there a way to turn this off? Is it possible to configure JIRA to let anyone assign them? Unlike the other lockdown stuff which prevents spam this doesn't seem like it could be a spam vector and it would be awesome to make it easier for people. -Jay On Sun, Feb 22, 2015 at 3:43 PM,

[jira] [Commented] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332452#comment-14332452 ] Jay Kreps commented on KAFKA-1865: -- Uploaded a new patch that tracks all incomplete Recor

[jira] [Commented] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332450#comment-14332450 ] Jay Kreps commented on KAFKA-1865: -- Updated reviewboard https://reviews.apache.org/r/3076

[jira] [Updated] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1865: - Attachment: KAFKA-1865_2015-02-22_16:26:46.patch > Add a flush() call to the new producer API > --

Re: Review Request 30763: Second attempt at flush()

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30763/ --- (Updated Feb. 23, 2015, 12:26 a.m.) Review request for kafka. Summary (update

[jira] [Updated] (KAFKA-1545) java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames

[ https://issues.apache.org/jira/browse/KAFKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-1545: --- Reviewer: Guozhang Wang Affects Version/s: 0.8.1.1 Status: Patch Available

[jira] [Commented] (KAFKA-1545) java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames

[ https://issues.apache.org/jira/browse/KAFKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332435#comment-14332435 ] ASF GitHub Bot commented on KAFKA-1545: --- GitHub user rekhajoshm opened a pull reques

[GitHub] kafka pull request: KAFKA-1545: KafkaHealthcheck.register failure

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/48 KAFKA-1545: KafkaHealthcheck.register failure KAFKA-1545: java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames You can merge this pull request into a

[jira] [Commented] (KAFKA-1416) Unify sendMessages/getMessages in unit tests

[ https://issues.apache.org/jira/browse/KAFKA-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332434#comment-14332434 ] Guozhang Wang commented on KAFKA-1416: -- [~futtre] I have assigned the ticket yo you,

[jira] [Updated] (KAFKA-1416) Unify sendMessages/getMessages in unit tests

[ https://issues.apache.org/jira/browse/KAFKA-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1416: - Assignee: Flutra Osmani > Unify sendMessages/getMessages in unit tests > -

[jira] [Commented] (KAFKA-1545) java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames

[ https://issues.apache.org/jira/browse/KAFKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332433#comment-14332433 ] ASF GitHub Bot commented on KAFKA-1545: --- Github user rekhajoshm closed the pull requ

[GitHub] kafka pull request: KAFKA-1545: KafkaHealthcheck.register failure

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

[jira] [Commented] (KAFKA-1545) java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames

[ https://issues.apache.org/jira/browse/KAFKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332432#comment-14332432 ] ASF GitHub Bot commented on KAFKA-1545: --- GitHub user rekhajoshm opened a pull reques

[GitHub] kafka pull request: KAFKA-1545: KafkaHealthcheck.register failure

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/47 KAFKA-1545: KafkaHealthcheck.register failure KAFKA-1545: java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames You can merge this pull request into a

Re: How to get a JIRA assigned

Hi Jonathan, You need to be added to the "contributor" list before can be assigned to jiras, and only committers can do that for you. I have just add you to the list so you should be able to assign yourself now. Guozhang On Sun, Feb 22, 2015 at 3:08 PM, Jonathan Rafalski < jonathan.rafal...@gma

[jira] [Updated] (KAFKA-1972) JMX Tool output for CSV format does not handle attributes with comma in their value

[ https://issues.apache.org/jira/browse/KAFKA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-1972: --- Reviewer: Jonathan Rafalski Status: Patch Available (was: Open) Patch at https://github.com/apa

[jira] [Updated] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated KAFKA-1621: --- Reviewer: Jay Kreps Status: Patch Available (was: Open) https://github.com/apache/kafka/pull/46

[jira] [Commented] (KAFKA-1621) Standardize --messages option in perf scripts

[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332423#comment-14332423 ] ASF GitHub Bot commented on KAFKA-1621: --- GitHub user rekhajoshm opened a pull reques

[GitHub] kafka pull request: KAFKA-1621 : Standardize --messages option

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/46 KAFKA-1621 : Standardize --messages option KAFKA-1621: Standardize --messages option in perf scripts You can merge this pull request into a Git repository by running: $ git pull https://github

How to get a JIRA assigned

Hello, I was wondering if there are any rights to be able to assign JIRA tickets to myself? I found what I think is a bug while working on 1679 so I opened a ticket and was going to assign a review board for both with my solution but now some else has attempted a patch. Just want to be able

[jira] [Updated] (KAFKA-1919) Metadata request issued with no backoff in new producer if there are no topics

[ https://issues.apache.org/jira/browse/KAFKA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1919: - Assignee: Jay Kreps > Metadata request issued with no backoff in new producer if there are no topi

[jira] [Commented] (KAFKA-1971) starting a broker with a conflicting id will delete the previous broker registration

[ https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332414#comment-14332414 ] Guozhang Wang commented on KAFKA-1971: -- I think that is because when the controller n

Re: [kafka-clients] Re: [VOTE] 0.8.2.1 Candidate 1

Jun, Can we also add https://issues.apache.org/jira/browse/KAFKA-1724 to the next RC please? Thanks! ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Sun, Feb 22, 2015 at 11:59 AM, Jun Rao wrote: > We identified at least one more bloc

[jira] [Commented] (KAFKA-1972) JMX Tool output for CSV format does not handle attributes with comma in their value

[ https://issues.apache.org/jira/browse/KAFKA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332387#comment-14332387 ] Rekha Joshi commented on KAFKA-1972: [~jrafalski] Patch at https://github.com/apache/k

[jira] [Commented] (KAFKA-1972) JMX Tool output for CSV format does not handle attributes with comma in their value

[ https://issues.apache.org/jira/browse/KAFKA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332386#comment-14332386 ] ASF GitHub Bot commented on KAFKA-1972: --- GitHub user rekhajoshm opened a pull reques

[GitHub] kafka pull request: KAFKA-1972: JMXTool multiple attributes

GitHub user rekhajoshm opened a pull request: https://github.com/apache/kafka/pull/45 KAFKA-1972: JMXTool multiple attributes KAFKA-1972: JMX Tool output for CSV format does not handle attributes with comma in their value You can merge this pull request into a Git repository by run

[jira] [Updated] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Malaska updated KAFKA-1961: --- Attachment: KAFKA-1961.4.patch Changed action from print statement to exception. Also updated unit te

[jira] [Commented] (KAFKA-1824) in ConsoleProducer - properties key.separator and parse.key no longer work

[ https://issues.apache.org/jira/browse/KAFKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332339#comment-14332339 ] Neha Narkhede commented on KAFKA-1824: -- [~gwenshap] I'm having trouble applying the p

Re: [DISCUSS] KIP-5 - Broker Configuration Management

Andrii, Thanks for updating the KIP. Few comments - Would you mind updating the Compatibility, Migration Plan section as well? We should discuss the new config store options - I'm not so sure that zookeeper is such a slam dunk choice for storing the configs. 1. Firstly, we have seen quite a

[jira] [Commented] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332270#comment-14332270 ] Gwen Shapira commented on KAFKA-1961: - Thank you [~ted.m]. Patch and test looks good

[jira] [Updated] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Malaska updated KAFKA-1961: --- Status: Patch Available (was: Open) The change makes it so the user can not delete topics that are co

[jira] [Updated] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Malaska updated KAFKA-1961: --- Attachment: KAFKA-1961.3.patch > Looks like its possible to delete _consumer_offsets topic > -

[jira] [Commented] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332268#comment-14332268 ] Ted Malaska commented on KAFKA-1961: Hey Gwen, Thank you for the help here is the lin

Re: [kafka-clients] Re: [VOTE] 0.8.2.1 Candidate 1

We identified at least one more blocker issue KAFKA-1971 during testing. So, we will have to roll another RC for 0.8.2.1. Thanks, Jun On Sat, Feb 21, 2015 at 6:04 PM, Joe Stein wrote: > Source verified, tests pass, quick start ok. > > Binaries verified, tests on scala > https://github.com/stea

[jira] [Commented] (KAFKA-1811) ensuring registered broker host:port is unique

[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332167#comment-14332167 ] Dave Parfitt commented on KAFKA-1811: - Chao Chu - sorry, I'm not able to finish workin

[jira] [Commented] (KAFKA-1811) ensuring registered broker host:port is unique

[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332106#comment-14332106 ] Chao Chu commented on KAFKA-1811: - Many thanks for your reply! [~metadave], are you still

[jira] [Commented] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332080#comment-14332080 ] Jiangjie Qin commented on KAFKA-1865: - Yes you are right, Jay. This approach sounds go