replication status

Hi, We didn't close any jira this week, but have patch under review for the following jiras. KAFKA-343: Leader election, become leader, become follower (v3. A,C) KAFKA-338: controller failover (V3. D) We have people signed up on the following jiras: KAFKA-350: Improve the highwatermark maintenanc

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408462#comment-13408462 ] Jun Rao commented on KAFKA-139: --- Derek, thanks for the new patch. A few more comments:

Re: [ANNOUNCEMENT] Apache Kafka 0.7.1-incubating Released

Could you do an svn cleanup there? It seems there are some unreleased locks. Thanks, Jun On Fri, Jul 6, 2012 at 12:40 PM, Joe Stein wrote: > will do > > svn up on /www/incubator.apache.org/content/kafka worked fine for me just > now, no problems > > On Thu, Jul 5, 2012 at

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408297#comment-13408297 ] Jun Rao commented on KAFKA-139: --- Derek, thanks for the patch. Some comments: 1. It woul

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408224#comment-13408224 ] Jun Rao commented on KAFKA-139: --- I applied the patch and did ./sbt +clean +package

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408074#comment-13408074 ] Jun Rao commented on KAFKA-139: --- Ok, maybe you can submit a patch with the sortedMap f

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408070#comment-13408070 ] Jun Rao commented on KAFKA-139: --- Also, I tried the patch for 0.7. What's the rig

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408062#comment-13408062 ] Jun Rao commented on KAFKA-139: --- Derek, For the 0.8 branch

[jira] [Commented] (KAFKA-139) cross-compile multiple Scala versions

[ https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407453#comment-13407453 ] Jun Rao commented on KAFKA-139: --- Thanks for the patch. Can't apply the patch to 0.

[jira] [Commented] (KAFKA-393) Add constructor for message which takes both byte array offset and length

[ https://issues.apache.org/jira/browse/KAFKA-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407252#comment-13407252 ] Jun Rao commented on KAFKA-393: --- Since this is not very critical, we probably should

[jira] [Commented] (KAFKA-379) TopicCount.constructTopicCount isn't thread-safe

[ https://issues.apache.org/jira/browse/KAFKA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407248#comment-13407248 ] Jun Rao commented on KAFKA-379: --- Thanks for the patch. In 0.7, the only usage of JSON i

Re: [ANNOUNCEMENT] Apache Kafka 0.7.1-incubating Released

Joe, Since this is still fresh in your mind, could you write a short description of the release process (probably under developer on the site) including copying the artifact to the dist directory? Also, are you still able to do svn up under /www/ incubator.apache.org/content/kafka? It complains t

[jira] [Commented] (KAFKA-383) copied the 0.7.0 release to the dist folder and update the site

[ https://issues.apache.org/jira/browse/KAFKA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407233#comment-13407233 ] Jun Rao commented on KAFKA-383: --- +1 > copied the 0.7.0 release to t

Re: Patch for SBT 0.11.3 / Scala 2.8.0,2.9.1,2.9.2 cross build

Derek, Thanks for your help. Could you attach the patch to this jira: https://issues.apache.org/jira/browse/KAFKA-139? Jun On Mon, Jul 2, 2012 at 8:34 AM, Derek Chen-Becker wrote: > I've put together an preliminary patch (attached) against kafka to build > using SBT 0.11.3 with a cross build a

[jira] [Commented] (KAFKA-343) revisit the become leader and become follower state change operations using V3 design

[ https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404797#comment-13404797 ] Jun Rao commented on KAFKA-343: --- Thanks for the patch. Overall, the patch looks promi

replication status

Hi, We closed the following jiras this week. KAFKA-339: Use multi-fetch for follower replication KAFKA-353: Tie Producer-side ack with high watermark and progress of replicas We have people signed up on the following jiras: KAFKA-350: Improve the highwatermark maintenance to handle failures KAFKA

[jira] [Updated] (KAFKA-376) expose different data to fetch requests from the follower replicas and consumer clients

[ https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-376: -- Summary: expose different data to fetch requests from the follower replicas and consumer clients (was: we need

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404182#comment-13404182 ] Jun Rao commented on KAFKA-353: --- It's ok to handle the remaining issues in separ

[jira] [Commented] (KAFKA-381) Changes made by a request does not affect following requests in the same packet.

[ https://issues.apache.org/jira/browse/KAFKA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404021#comment-13404021 ] Jun Rao commented on KAFKA-381: --- The problem is likely due to what Guozhang described

Re: Is DefaultEventHandler.collate sort order important?

Derek, The ordering of those ProducerRequests doesn't really matter. It seems that the easiest way to fix this is to ask EasyMock to ignore ordering. Thanks, Jun On Fri, Jun 29, 2012 at 9:03 AM, Derek Chen-Becker wrote: > I'm working on a patch to allow for cross-building kafka to both scala

[jira] [Commented] (KAFKA-382) Write ordering guarantee violated

[ https://issues.apache.org/jira/browse/KAFKA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404010#comment-13404010 ] Jun Rao commented on KAFKA-382: --- Currently, each produce request blocks on a response, w

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403640#comment-13403640 ] Jun Rao commented on KAFKA-353: --- A few more comments on patch v3:

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403221#comment-13403221 ] Jun Rao commented on KAFKA-353: --- Thanks for patch v2. A couple of more comments:

Re: Build emails

Chris, Thanks for setting this up. For 0.8, unit tests seems\ to pass. It fails at generating java docs, which is weird. Jun On Wed, Jun 27, 2012 at 3:33 PM, Chris Burroughs wrote: > By popular demand build emails now go to > kafka-comm...@incubator.apache.org and we have per branch builds: >

[jira] [Commented] (KAFKA-378) mirrors but must never be used for verification

[ https://issues.apache.org/jira/browse/KAFKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403148#comment-13403148 ] Jun Rao commented on KAFKA-378: --- +1 > mirrors but must never be u

[jira] [Commented] (KAFKA-377) some of the dist mirrors are giving a 403

[ https://issues.apache.org/jira/browse/KAFKA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403141#comment-13403141 ] Jun Rao commented on KAFKA-377: --- +1 > some of the dist mirrors are g

Re: [ANNOUNCEMENT] Apache Kafka 0.7.1-incubating Released

o change the link in the download to by pass the mirrors and go > straight to > http://www.apache.org/dist/incubator/kafka/kafka-0.7.1-incubating/ > relative for each link? > > On Thu, Jun 28, 2012 at 12:22 AM, Jun Rao wrote: > > > Joe, > > > > When I cl

Re: [ANNOUNCEMENT] Apache Kafka 0.7.1-incubating Released

Joe, When I clicked the download link, I got permission denied. Thanks, Jun On Wed, Jun 27, 2012 at 5:55 PM, Joe Stein wrote: > Hi. > > The Apache Kafka team is pleased to announce the release of > Kafka 0.7.1-incubating. > > This is the second incubating release of Apache Kafka, a > distribu

Re: 0.7.1 almost out the door...

Joe, Made a comment on the jira. Once that's fixed, we can commit the site change. To update the site in Apache, do the following: login to people.apache.org; go to /www/incu

[jira] [Commented] (KAFKA-375) update the site page for the 0.7.1 release download and related changes

[ https://issues.apache.org/jira/browse/KAFKA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402472#comment-13402472 ] Jun Rao commented on KAFKA-375: --- Looks good. The only thing is that message format

[jira] [Commented] (KAFKA-374) Move to java CRC32 implementation

[ https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402349#comment-13402349 ] Jun Rao commented on KAFKA-374: --- Should the native and the java column be reversed? Now

[jira] [Assigned] (KAFKA-362) ZookeeperConsumerConnector needs to connect to new leader after leadership change

[ https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-362: - Assignee: Jun Rao > ZookeeperConsumerConnector needs to connect to new leader after leaders

[jira] [Created] (KAFKA-376) we need to expose different data to fetch requests from the follower replicas and consumer clients

Jun Rao created KAFKA-376: - Summary: we need to expose different data to fetch requests from the follower replicas and consumer clients Key: KAFKA-376 URL: https://issues.apache.org/jira/browse/KAFKA-376

[jira] [Commented] (KAFKA-372) Consumer doesn't receive all data if there are multiple segment files

[ https://issues.apache.org/jira/browse/KAFKA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401491#comment-13401491 ] Jun Rao commented on KAFKA-372: --- Thanks John for reviewing the patch. Committed to

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401447#comment-13401447 ] Jun Rao commented on KAFKA-353: --- 3.4 I overlooked that watcher.collectSatisfiedRequest

[jira] [Updated] (KAFKA-372) Consumer doesn't receive all data if there are multiple segment files

[ https://issues.apache.org/jira/browse/KAFKA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-372: -- Attachment: kafka-372_v1.patch There were several issues that caused the problem. 1. Log.nextAppendOffset

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400682#comment-13400682 ] Jun Rao commented on KAFKA-353: --- The race condition that Jay raised seems like a poten

Re: RC3 status

AM, Neha Narkhede >wrote: > > > Joe, > > > > It will be good to make the release available in the Kafka directory > > at /www/www.apache.org/dist - > > > > > http://incubator.apache.org/guides/releasemanagement.html#understanding-distribution > >

Re: RC3 status

n achieved with respect to IPMC votes Given the following votes, I think our release has passed. Chris Douglas (PPMC/IPMC) + 1 Kevan Miller (IPMC)- 1 Jun Rao (PPMC) + 1 Jakob Homan (PPMC/IPMC) + 1 Please tally the votes and inform general@incubator and kafka-dev. The next step is to change the websi

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400204#comment-13400204 ] Jun Rao commented on KAFKA-353: --- The suggestions for future improvements all make sense

[jira] [Commented] (KAFKA-353) tie producer-side ack with high watermark and progress of replicas

[ https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400201#comment-13400201 ] Jun Rao commented on KAFKA-353: --- Thanks for patch v1. Looks good overall. Some comments

[jira] [Updated] (KAFKA-339) using MultiFetch in the follower

[ https://issues.apache.org/jira/browse/KAFKA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-339: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the review. Committed patch v2

[jira] [Commented] (KAFKA-338) controller failover

[ https://issues.apache.org/jira/browse/KAFKA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399838#comment-13399838 ] Jun Rao commented on KAFKA-338: --- Prashanth, Thanks for signing up for this jira. One t

replication status

Hi, We closed the following jira this week. A few other jiras have patches and are under review. KAFKA-329: Create topic support (revisit based on v3 design) We have people signed up on the following jiras: KAFKA-339: Use multi-fetch for follower replication KAFKA-350: Improve the highwatermark

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)

Alan, I found the list of jars that you published during the 0.7.0 release. The new jars in the 0.7.1 release are the following: commons-cli: AL2 commons-el: AL2 commons-net: AL2 commons-io: AL2 commons-compress: AL2 core: Eclipse Public License 1.0 hsqldb: BSD jasper-compiler: AL2 jasper-runtime:

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)

27;s not true. There are a significant number of new jars. > >> > >>> That was deemed acceptable and so without a > >>> lot of new directives, which don't seem to be clear here, so should > >>> this one. > >>> > >>> Bind

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)

ding). > > That's not true. There are a significant number of new jars. > > > That was deemed acceptable and so without a > > lot of new directives, which don't seem to be clear here, so should > > this one. > > > > Binding +1 on RC3. > > > &g

[jira] [Resolved] (KAFKA-370) Exception "java.util.NoSuchElementException: None.get" appears inconsistently in Mirror Maker log.

[ https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-370. --- Resolution: Fixed Fix Version/s: 0.8 Assignee: Jun Rao Thanks for the review. Committed to

[jira] [Commented] (KAFKA-306) broker failure system test broken on replication branch

[ https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399439#comment-13399439 ] Jun Rao commented on KAFKA-306: --- Thanks for patch v4. A few more comments: 21.2 KAFA

[jira] [Updated] (KAFKA-370) Exception "java.util.NoSuchElementException: None.get" appears inconsistently in Mirror Maker log.

[ https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-370: -- Attachment: kafka-370_v1.patch Attach patch v1. The issue is that the code relies on the broker ids in the

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)

Alan, I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades, the only added jar in 0.7.1 is the following. ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar Snappy is on Apache License 2.0. So, our licenses should be covered. Thanks, Jun On Thu, Jun 21, 2012 at 9

[jira] [Commented] (KAFKA-342) revisit the broker startup procedure according to V3 design

[ https://issues.apache.org/jira/browse/KAFKA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399039#comment-13399039 ] Jun Rao commented on KAFKA-342: --- Prashanth, Thanks for volunteering. It turns out that

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)

+1 on the release. Run quickstart and unit tests. All good. Thanks, Jun On Wed, Jun 20, 2012 at 9:19 AM, Joe Stein wrote: > Hello, > > This is the third candidate for the second incubator release for Apache > Kafka, version 0.7.1-incubating. > > This release fixes the following issues > > htt

[jira] [Commented] (KAFKA-306) broker failure system test broken on replication branch

[ https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397691#comment-13397691 ] Jun Rao commented on KAFKA-306: --- Thanks for patch v2. Some comments: 21. run_test.sh

[jira] [Created] (KAFKA-369) remove ZK dependency on producer

Jun Rao created KAFKA-369: - Summary: remove ZK dependency on producer Key: KAFKA-369 URL: https://issues.apache.org/jira/browse/KAFKA-369 Project: Kafka Issue Type: Sub-task Components

[jira] [Updated] (KAFKA-337) upgrade ZKClient to allow conditional updates in ZK

[ https://issues.apache.org/jira/browse/KAFKA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-337: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to 0.8 > upgr

[jira] [Updated] (KAFKA-339) using MultiFetch in the follower

[ https://issues.apache.org/jira/browse/KAFKA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-339: -- Attachment: kafka-339_v2.patch Thanks for the review. Attaching patch v2. AbstractFetcher: - currentOffset

[jira] [Commented] (KAFKA-368) use the pig core jar from maven instead of distributing it

[ https://issues.apache.org/jira/browse/KAFKA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397087#comment-13397087 ] Jun Rao commented on KAFKA-368: --- +1 Just make sure that the pig-0.8.0 jar files are rem

Re: remaining jars in svn (was Fwd: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2))

like > this > > is > > > how your last release was packaged, also… I don't know if this is a > > > blocking issue (for an incubator release), but I think you need to work > > on > > > resolving this (i.e. remove binaries from your source)… > > > > > &

Fwd: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)

-- Forwarded message -- From: Jun Rao Date: Mon, Jun 18, 2012 at 9:49 PM Subject: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2) To: gene...@incubator.apache.org Joe, It looks like that we need to create a new RC. Could you pick up kafka-366? It just adds a new jmx

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)

tifacts is… and whether or not they conform to > ASF standards (I did not review them all). Your project needs to document > them. > > FYI, I couldn't figure out from the documentation how to start a server > after I built kafka. > > --kevan > > On Jun 18, 2012,

[jira] [Updated] (KAFKA-366) add jmx beans in broker to track # bytes in consumer

[ https://issues.apache.org/jira/browse/KAFKA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-366: -- Resolution: Fixed Fix Version/s: 0.7.1 0.8 Status: Resolved (was: Patch

[jira] [Assigned] (KAFKA-366) add jmx beans in broker to track # bytes in consumer

[ https://issues.apache.org/jira/browse/KAFKA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-366: - Assignee: Jun Rao > add jmx beans in broker to track # bytes in consu

[jira] [Updated] (KAFKA-366) add jmx beans in broker to track # bytes in consumer

[ https://issues.apache.org/jira/browse/KAFKA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-366: -- Status: Patch Available (was: Open) Patch for trunk attached. Will port to 0.8 branch after committing to

[jira] [Updated] (KAFKA-366) add jmx beans in broker to track # bytes in consumer

[ https://issues.apache.org/jira/browse/KAFKA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-366: -- Attachment: kafka-366_v1.patch > add jmx beans in broker to track # bytes in consu

[jira] [Created] (KAFKA-366) add jmx beans in broker to track # bytes in consumer

Jun Rao created KAFKA-366: - Summary: add jmx beans in broker to track # bytes in consumer Key: KAFKA-366 URL: https://issues.apache.org/jira/browse/KAFKA-366 Project: Kafka Issue Type: Improvement

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)

Any other voters? Thanks, Jun On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein wrote: > Hello, > > This is the second candidate for the second incubator release for Apache > Kafka, version 0.7.1-incubating. > > This release fixes the following issues > > http://people.apache.org/~joestein/kafka-0.7

[jira] [Reopened] (KAFKA-348) rebase 0.8 branch from trunk

[ https://issues.apache.org/jira/browse/KAFKA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reopened KAFKA-348: --- Reopen the jira. Found a few missed merges and included them in kafka-348-delta.patch. > reb

[jira] [Updated] (KAFKA-348) rebase 0.8 branch from trunk

[ https://issues.apache.org/jira/browse/KAFKA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-348: -- Attachment: kafka-348-delta.patch > rebase 0.8 branch from tr

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)

Can other people (including mentors) help vote on this release? Thanks, Jun On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein wrote: > Hello, > > This is the second candidate for the second incubator release for Apache > Kafka, version 0.7.1-incubating. > > This release fixes the following issues >

Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)

+1 Ran quick start, unit tests and rat tests. Thanks, Jun On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein wrote: > Hello, > > This is the second candidate for the second incubator release for Apache > Kafka, version 0.7.1-incubating. > > This release fixes the following issues > > http://people.a

[jira] [Updated] (KAFKA-339) using MultiFetch in the follower

[ https://issues.apache.org/jira/browse/KAFKA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-339: -- Status: Patch Available (was: Open) Uploaded patch v1. Created an AbstractFetcher and AbstractFetcherManager

[jira] [Updated] (KAFKA-339) using MultiFetch in the follower

[ https://issues.apache.org/jira/browse/KAFKA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-339: -- Attachment: kafka-339_v1.patch > using MultiFetch in the follo

video recording for the 1st Kafka user group meeting

Thanks for everyone who showed up for the user group meeting last night. It was a good turnout and was very interactive. If you missed the event, the video recording can be found at https://cwiki.apache.org/confluence/display/KAFKA/Kafka+papers+and+presentations Jun

[jira] [Commented] (KAFKA-365) change copyright in NOTICE to 2012

[ https://issues.apache.org/jira/browse/KAFKA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295182#comment-13295182 ] Jun Rao commented on KAFKA-365: --- +1 on the patch. > change copyr

[jira] [Updated] (KAFKA-341) Create a new single host system test to validate all replicas on 0.8 branch

[ https://issues.apache.org/jira/browse/KAFKA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-341: -- Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) John, thanks

Re: Consumer re-design proposal

If nobody objects, we can create a separate consumer redesign branch. This way, everyone can see the changes and progress. Thanks, Jun On Mon, Jun 11, 2012 at 4:52 PM, Neha Narkhede wrote: > Hi, > > Over the past few months, we've received quite a lot of feedback on the > consumer side features

[jira] [Resolved] (KAFKA-335) Implement an embedded controller

[ https://issues.apache.org/jira/browse/KAFKA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-335. --- Resolution: Fixed Thanks for the patch. Just committed to 0.8 branch. > Implement

Re: [DISCUSSION] KAFKA 0.7.1 RELEASE

e then it can get merged. > > I have created the branch for the release. > > On Mon, Jun 11, 2012 at 10:56 AM, Jun Rao wrote: > > > Joe, > > > > Thanks for driving this. > > > > For 1), KAFKA-345 and KAFKA-346 (depends on KAFAK-345) are being worked &g

[jira] [Commented] (KAFKA-335) Implement an embedded controller

[ https://issues.apache.org/jira/browse/KAFKA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294758#comment-13294758 ] Jun Rao commented on KAFKA-335: --- A few more comments for v5 patch. 41. KafkaContro

[jira] [Commented] (KAFKA-329) Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

[ https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294695#comment-13294695 ] Jun Rao commented on KAFKA-329: --- Prahsanth, I was trying to figure out

[jira] [Commented] (KAFKA-329) Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

[ https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294581#comment-13294581 ] Jun Rao commented on KAFKA-329: --- Prashanth, Thanks for patch v1. Some comments:

[jira] [Commented] (KAFKA-335) Implement an embedded controller

[ https://issues.apache.org/jira/browse/KAFKA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294550#comment-13294550 ] Jun Rao commented on KAFKA-335: --- Thanks for patch v3. A few more comments:

[jira] [Commented] (KAFKA-341) Create a new single host system test to validate all replicas on 0.8 branch

[ https://issues.apache.org/jira/browse/KAFKA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293958#comment-13293958 ] Jun Rao commented on KAFKA-341: --- For sleep time, could we make it more adaptive? Basic

[jira] [Commented] (KAFKA-329) Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

[ https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293764#comment-13293764 ] Jun Rao commented on KAFKA-329: --- Thanks for draft v2. Some quick comments:

[jira] [Commented] (KAFKA-306) broker failure system test broken on replication branch

[ https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293752#comment-13293752 ] Jun Rao commented on KAFKA-306: --- Sorry, just got to review this. Trunk has moved, could

[jira] [Commented] (KAFKA-341) Create a new single host system test to validate all replicas on 0.8 branch

[ https://issues.apache.org/jira/browse/KAFKA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293745#comment-13293745 ] Jun Rao commented on KAFKA-341: --- Thanks for patch v2. I kept getting the following excep

[jira] [Commented] (KAFKA-335) Implement an embedded controller

[ https://issues.apache.org/jira/browse/KAFKA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293728#comment-13293728 ] Jun Rao commented on KAFKA-335: --- For 4.3, could you create a separate jira to track

[jira] [Commented] (KAFKA-335) Implement an embedded controller

[ https://issues.apache.org/jira/browse/KAFKA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293702#comment-13293702 ] Jun Rao commented on KAFKA-335: --- Thanks for patch v2. Some more comments:

[jira] [Commented] (KAFKA-329) Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

[ https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292872#comment-13292872 ] Jun Rao commented on KAFKA-329: --- Prashanth, Thanks for patch. Some comments

Re: [DISCUSSION] KAFKA 0.7.1 RELEASE

Joe, Thanks for driving this. For 1), KAFKA-345 and KAFKA-346 (depends on KAFAK-345) are being worked on. It would be nice to include them in 0.7.1. However, it involves a consumer API change and we have to be a bit more careful. So, deferring it to 0.7.2 maybe ok too. It really depends on how cr

kafka replication status

Hi, As of this week, we closed KAFKA-336 (for controller to send requests to brokers). We have people signed up on the following jiras: KAFKA-335: Embedded controller KAFKA-329: Create topic support (revisit based on v3 design) KAFKA-339: Use multi-fetch for follower replication The following j

Re: Kafka user group meeting

Ok, I have created the following event for the 1st Apache Kafka user group meeting. Feel free to send it around. See you on Jun 14. http://linkd.in/Kpn6XH Thanks, Jun On Fri, Jun 8, 2012 at 10:24 AM, Jun Rao wrote: > Yes. > > Date: Jun 14 > Time: 7:00pm-8:30pm > Location: Lin

[jira] [Commented] (KAFKA-335) Implement an embedded controller

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

Re: [DISCUSS] Graduate from incubator?

Actually, any committers outside of LinkedIn is interested in drive an 0.7.1 release? That will help diversifying the community. It should be much easier than the 0.7.0 release since most of the licensing issues have been resolved. Thanks, Jun On Wed, Jun 6, 2012 at 5:46 PM, Joel Koshy wrote:

Re: Kafka user group meeting

Anyone else plan to attend the Kafka user group meeting on Jun 14? I'd like to get a rough head count to arrange facility and food, etc. Thanks, Jun On Thu, Jun 7, 2012 at 4:20 PM, Jun Rao wrote: > How about having a Kafka user group meeting on Jun 14, say from 7:00pm to > 8:30pm

[jira] [Commented] (KAFKA-329) Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

[ https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291542#comment-13291542 ] Jun Rao commented on KAFKA-329: --- Prashanth, Do you plan to work on this jira anytime

Re: Kafka user group meeting

> > Definitely Interested. > > > > Content: > > A. tutorial (walk through the kafka source code at high level) , new > > features, operations, > > B. Q/A session > > > > On Tue, Jun 5, 2012 at 3:22 PM, Jun Rao wrote: > > > > > Hi, > > >

[jira] [Commented] (KAFKA-341) Create a new single host system test to validate all replicas on 0.8 branch

[ https://issues.apache.org/jira/browse/KAFKA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290215#comment-13290215 ] Jun Rao commented on KAFKA-341: --- Thanks for the patch. Some comments: 1. Can we reuse k

[jira] [Updated] (KAFKA-336) add an admin RPC to communicate state changes between the controller and the broker

[ https://issues.apache.org/jira/browse/KAFKA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-336: -- Resolution: Fixed Status: Resolved (was: Patch Available) Fixed as part of kafka-349

<    2   3   4   5   6   7   8   9   10   11   >