[jira] [Commented] (KAFKA-1534) transient unit test failure in testBasicPreferredReplicaElection

[ https://issues.apache.org/jira/browse/KAFKA-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128072#comment-14128072 ] Abhishek Sharma commented on KAFKA-1534: I would like to work on it. Please mentio

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128042#comment-14128042 ] Abhishek Sharma commented on KAFKA-1501: [~copester] - Are you running './gradlew

Re: Error handling in new Java Producer

Hi Steve, You can try to reduce the metadata.fetch.timeout.ms config value, which will controll how much the send() call can be blocked upon broker metadata not available (due to broker itself not available). Guozhang On Tue, Sep 9, 2014 at 7:00 PM, Tarzia wrote: > Thanks Guozhang, > > Another

Re: Error handling in new Java Producer

Thanks Guozhang, Another case I am seeing is that producer.send() seems to block when the brokers are unavailable. This is not the behavior I want (I would rather have it throw an exception immediately so I can queue the messages for replay). I will try to confirm this tomorrow. -Steve On

[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-tabpanel&focusedCommentId=14127936#comment-14127936 ] Guozhang Wang commented on KAFKA-1590: -- I think the first option 1) could work, [~jkr

Re: Error handling in new Java Producer

Hi Steve: 1. the new producer will be included in the 0.8.2 release for production usage. 2. The error you reported has been changed as a WARN in the latest trunk. We realize this should not really be an error case. In general, any errors will be propagated to the producer in the following two way

[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=14127899#comment-14127899 ] Otis Gospodnetic commented on KAFKA-1481: - Here is a Kafka user who said: {quote}

Re: Need Document and Explanation Of New Metrics Name in New Java Producer on Kafka Trunk

Thanks, I was using without JMX. I will go through doc. But how about Topic or Metric name Topic Name Convention or Metric Name Convention ? The dot notation with topic having a ".". Any future plan to enforce some stand rules. Thanks, Bhavesh On Tue, Sep 9, 2014 at 3:38 PM, Jay Kreps wrote

[jira] [Updated] (KAFKA-1477) add authentication layer and initial JKS x509 implementation for brokers, producers and consumer for network communication

[ https://issues.apache.org/jira/browse/KAFKA-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1477: --- Fix Version/s: (was: 0.8.2) 0.9.0 > add authentication layer and initial JKS x509 imple

[jira] [Resolved] (KAFKA-1533) transient unit test failure in ProducerFailureHandlingTest

[ https://issues.apache.org/jira/browse/KAFKA-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1533. Resolution: Fixed Yes, logging the InetAddress is fine. To get the remoteAddress, we will have to check if

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127730#comment-14127730 ] David Chen commented on KAFKA-1627: --- I see. That makes sense. I'll close this ticket. >

[jira] [Resolved] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Chen resolved KAFKA-1627. --- Resolution: Not a Problem This was already done. > Move to Git > --- > > Key:

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127703#comment-14127703 ] Jay Kreps commented on KAFKA-1501: -- That's awesome, thanks for digging in on this. > tra

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127702#comment-14127702 ] Jay Kreps commented on KAFKA-1627: -- Unfortunately the website has to remain on svn as apa

Re: Need Document and Explanation Of New Metrics Name in New Java Producer on Kafka Trunk

Hi Bhavesh, Each of those JMX attributes comes with documentation. If you open up jconsole and attach to a jvm running the consumer you should be able to read the descriptions for each attribute. -Jay On Tue, Sep 9, 2014 at 2:07 PM, Bhavesh Mistry wrote: > Kafka Team, > > Can you please let me

[jira] [Updated] (KAFKA-1625) Sample Java code contains Scala syntax

[ https://issues.apache.org/jira/browse/KAFKA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Chen updated KAFKA-1625: -- Attachment: KAFKA-1625.site.2.patch Attaching a new patch that re-fully-qualifies class names. > Sample

Need Document and Explanation Of New Metrics Name in New Java Producer on Kafka Trunk

Kafka Team, Can you please let me know what each of following Metrics means ? Some of them are obvious, but some are hard to understand. My Topic name is *TOPIC_NAME*. can we enforce a Topic Name Convention or Metric Name Convention. Because in previous version of Kafka, we have similar issue

[jira] [Commented] (KAFKA-1625) Sample Java code contains Scala syntax

[ https://issues.apache.org/jira/browse/KAFKA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127553#comment-14127553 ] Joel Koshy commented on KAFKA-1625: --- Not that I know of, but the new producer is impleme

[jira] [Commented] (KAFKA-1625) Sample Java code contains Scala syntax

[ https://issues.apache.org/jira/browse/KAFKA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127547#comment-14127547 ] David Chen commented on KAFKA-1625: --- Sounds good. Do we have plans to consolidate the cl

[jira] [Commented] (KAFKA-1625) Sample Java code contains Scala syntax

[ https://issues.apache.org/jira/browse/KAFKA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127529#comment-14127529 ] Joel Koshy commented on KAFKA-1625: --- Thanks for pointing out the reference to scala code

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127474#comment-14127474 ] David Chen commented on KAFKA-1627: --- Ah, sorry I missed that. However, it looks like th

[GitHub] kafka pull request: Merge pull request #1 from apache/trunk

GitHub user copester opened a pull request: https://github.com/apache/kafka/pull/32 Merge pull request #1 from apache/trunk Fork sync You can merge this pull request into a Git repository by running: $ git pull https://github.com/ResilientScience/kafka trunk Alternatively you

[GitHub] kafka pull request: Merge pull request #1 from apache/trunk

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

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127343#comment-14127343 ] Chris Cope commented on KAFKA-1501: --- Ugh, this bug was obnoxious! This has bit us a enou

Re: Review Request 25136: Patch for KAFKA-1610

> On Sept. 9, 2014, 1:38 a.m., Joel Koshy wrote: > > core/src/main/scala/kafka/admin/ReassignPartitionsCommand.scala, line 125 > > > > > > I don't think this is required, since we are subsequently doing a map > > over

[jira] [Commented] (KAFKA-1501) transient unit tests failures due to port already in use

[ https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127178#comment-14127178 ] Abhishek Sharma commented on KAFKA-1501: [~junrao] Can you please suggest how to r

[jira] [Commented] (KAFKA-1482) Transient test failures for kafka.admin.DeleteTopicTest

[ https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127162#comment-14127162 ] Sriharsha Chintalapani commented on KAFKA-1482: --- [~junrao] [~guozhang] Is th

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126968#comment-14126968 ] Jarek Jarcec Cecho commented on KAFKA-1627: --- Thanks, I've missed that [~joestein

[jira] [Commented] (KAFKA-1627) Move to Git

[ https://issues.apache.org/jira/browse/KAFKA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126963#comment-14126963 ] Joe Stein commented on KAFKA-1627: -- Thanks, we made this transition a couple years back a