Re: Inconsistent latency with replication

This is probably caused by the general issue in purgatory. Basically, the check on whether a request is satisfied or not and the watcher registration is not atomic. So, in this case, when a replica fetch request comes in, it could be that the byte check is not satisfied, but before the fetch reques

The consumer performance test seems to be totally broken

It loops on for (messageAndMetadata <- stream if messagesRead < config.numMessages) { // count message } That means it loops over *all* messages in the stream (eventually blocking when all messages are exhausted) but only counts the first N as determined by the config. As a result this comma

Re: Inconsistent latency with replication

Also set to the default, which is 1. -Jay On Sat, Feb 8, 2014 at 1:31 PM, Sriram Subramanian < srsubraman...@linkedin.com> wrote: > What is replica.fetch.min.bytes set to? > > On 2/8/14 1:22 PM, "Jay Kreps" wrote: > > >Hey guys, > > > >I was running the end-to-end latency test (kafka.TestEndTo

Re: Inconsistent latency with replication

What is replica.fetch.min.bytes set to? On 2/8/14 1:22 PM, "Jay Kreps" wrote: >Hey guys, > >I was running the end-to-end latency test (kafka.TestEndToEndLatency) and >saw something a little weird. This test runs a producer and a consumer and >sends a single message at a time and measures the rou

Inconsistent latency with replication

Hey guys, I was running the end-to-end latency test (kafka.TestEndToEndLatency) and saw something a little weird. This test runs a producer and a consumer and sends a single message at a time and measures the round-trip time from the producer's send to the consumer getting the message. With repli

Re: protocol definition

On 2/8/14 11:40 AM, Jay Kreps wrote: In general I think we have tried to make the protocol consistent. The one exception might be some details of the message set itself. This is handled by custom code still in the new producer as we pack these structures ahead of time. I agree that it is very co

[jira] [Updated] (KAFKA-330) Add delete topic support

[ https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-330: Attachment: KAFKA-330_2014-02-08_11:07:37.patch > Add delete topic support > --

[jira] [Commented] (KAFKA-330) Add delete topic support

[ https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895690#comment-13895690 ] Neha Narkhede commented on KAFKA-330: - Updated reviewboard https://reviews.apache.org/r

Re: Review Request 17460: Patch for KAFKA-330

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/17460/ --- (Updated Feb. 8, 2014, 7:07 p.m.) Review request for kafka. Bugs: KAFKA-330

Re: Preparing for 0.8.1 release

I have started capturing the 0.8.1 build issue as sub tickets under https://issues.apache.org/jira/browse/KAFKA-1243 /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop

[jira] [Created] (KAFKA-1249) release tar name is different than 0.8.0

Joe Stein created KAFKA-1249: Summary: release tar name is different than 0.8.0 Key: KAFKA-1249 URL: https://issues.apache.org/jira/browse/KAFKA-1249 Project: Kafka Issue Type: Sub-task Affec

[jira] [Created] (KAFKA-1248) jars are missing from maven upload that were previously there

Joe Stein created KAFKA-1248: Summary: jars are missing from maven upload that were previously there Key: KAFKA-1248 URL: https://issues.apache.org/jira/browse/KAFKA-1248 Project: Kafka Issue Ty

[jira] [Resolved] (KAFKA-1162) handle duplicate entry for ZK in the pom file

[ https://issues.apache.org/jira/browse/KAFKA-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein resolved KAFKA-1162. -- Resolution: Won't Fix moved from sbt to gradle, this was a sbt problem > handle duplicate entry for ZK

[jira] [Resolved] (KAFKA-1160) have the pom reference the exclusions necessary so folks don't have to

[ https://issues.apache.org/jira/browse/KAFKA-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein resolved KAFKA-1160. -- Resolution: Won't Fix moved from sbt to gradle, this was a sbt problem > have the pom reference the ex

[jira] [Updated] (KAFKA-121) pom should include standard maven niceties

[ https://issues.apache.org/jira/browse/KAFKA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-121: Issue Type: Sub-task (was: Improvement) Parent: KAFKA-1243 > pom should include standard maven nice

[jira] [Updated] (KAFKA-121) pom should include standard maven niceties

[ https://issues.apache.org/jira/browse/KAFKA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-121: Attachment: kafka_2.10.1-0.8.1.pom attached is the pom generated by the gradle build we can use this ticket

[jira] [Updated] (KAFKA-1247) 2.9.2 maven jars are now showing up

[ https://issues.apache.org/jira/browse/KAFKA-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1247: - Priority: Blocker (was: Major) > 2.9.2 maven jars are now showing up > -

[jira] [Created] (KAFKA-1247) 2.9.2 maven jars are now showing up

Joe Stein created KAFKA-1247: Summary: 2.9.2 maven jars are now showing up Key: KAFKA-1247 URL: https://issues.apache.org/jira/browse/KAFKA-1247 Project: Kafka Issue Type: Bug Reporte

[jira] [Created] (KAFKA-1246) The 2.10 version is showing up as 2.10.1

Joe Stein created KAFKA-1246: Summary: The 2.10 version is showing up as 2.10.1 Key: KAFKA-1246 URL: https://issues.apache.org/jira/browse/KAFKA-1246 Project: Kafka Issue Type: Sub-task Affec

[jira] [Created] (KAFKA-1245) the jar files and pom are not being signed so nexus is failing to publish them

Joe Stein created KAFKA-1245: Summary: the jar files and pom are not being signed so nexus is failing to publish them Key: KAFKA-1245 URL: https://issues.apache.org/jira/browse/KAFKA-1245 Project: Kafka

[jira] [Created] (KAFKA-1244) The LICENSE and NOTICE are missing from the jar files

Joe Stein created KAFKA-1244: Summary: The LICENSE and NOTICE are missing from the jar files Key: KAFKA-1244 URL: https://issues.apache.org/jira/browse/KAFKA-1244 Project: Kafka Issue Type: Sub-t

[jira] [Created] (KAFKA-1243) Gradle issues for release

Joe Stein created KAFKA-1243: Summary: Gradle issues for release Key: KAFKA-1243 URL: https://issues.apache.org/jira/browse/KAFKA-1243 Project: Kafka Issue Type: Bug Affects Versions: 0.8.1

Re: Review Request 17460: Patch for KAFKA-330

> On Feb. 8, 2014, 2:43 a.m., Joel Koshy wrote: > > Already checked-in so this is really a follow-up review. > > > > My overall take on the implementation is that it is (perhaps - because I'm > > not 100 percent sure myself) complex mainly to handle corner cases which are > > rare but I think re

Re: protocol definition

In general I think we have tried to make the protocol consistent. The one exception might be some details of the message set itself. This is handled by custom code still in the new producer as we pack these structures ahead of time. There isn't a way to ask for the latest api version. We could add