[jira] [Commented] (KAFKA-2087) TopicConfigManager javadoc references incorrect paths

[ https://issues.apache.org/jira/browse/KAFKA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396083#comment-14396083 ] Aditya Auradkar commented on KAFKA-2087: [~jkreps] Yeah, I've discarded that patch

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396077#comment-14396077 ] Gwen Shapira commented on KAFKA-1809: - Quick summary of changes since [~jjkoshy] and [

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396071#comment-14396071 ] Gwen Shapira commented on KAFKA-1809: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1809: Attachment: KAFKA-1809_2015-04-04_22:00:13.patch > Refactor brokers to allow listening on multiple p

Re: Review Request 28769: Patch for KAFKA-1809

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28769/ --- (Updated April 5, 2015, 5 a.m.) Review request for kafka. Bugs: KAFKA-1809

[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=14396053#comment-14396053 ] Gwen Shapira commented on KAFKA-1501: - woops. You are right [~jkreps], I overlooked it

Re: Chicken and egg problem when initializing SocketServer

Thanks. I think I found a solution that doesn't take new locks or buffers: 1. Change the portProtocol map to ConcurrentHashMap (which makes it both thread-safe and mutable). Initialize as empty map. 2. Initialize both processors and acceptors with the hashmap, also tell each acceptor which protoco

[jira] [Commented] (KAFKA-1631) ReplicationFactor and under-replicated partitions incorrect during reassignment

[ https://issues.apache.org/jira/browse/KAFKA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396039#comment-14396039 ] Jay Kreps commented on KAFKA-1631: -- Is this behavior really so bad? I actually think hand

Jenkins build is back to normal : KafkaPreCommit #56

See

[jira] [Commented] (KAFKA-2087) TopicConfigManager javadoc references incorrect paths

[ https://issues.apache.org/jira/browse/KAFKA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396036#comment-14396036 ] Jay Kreps commented on KAFKA-2087: -- [~aauradkar] this doesn't look like a javadoc patch..

[jira] [Resolved] (KAFKA-1005) kafka.perf.ConsumerPerformance not shutting down consumer

[ https://issues.apache.org/jira/browse/KAFKA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1005. -- Resolution: Fixed Committed. > kafka.perf.ConsumerPerformance not shutting down consumer >

[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=14396030#comment-14396030 ] Jay Kreps commented on KAFKA-1501: -- [~gwenshap] I think the bounce tests in both the prod

Re: Chicken and egg problem when initializing SocketServer

Hi Gwen, Can we buffer the requests that arrive before acceptors are up. Once we have the acceptors, the buffer can be cleared. However, this adds on to the complexity. On Sunday, April 5, 2015, Gwen Shapira wrote: > Hi, > > I'm trying to rebase KAFKA-1809 after KAFKA-1501 was committed, and I'

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396024#comment-14396024 ] Evan Huus commented on KAFKA-2082: -- If the root of this bug is the controller not returni

[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=14396023#comment-14396023 ] Chris Cope commented on KAFKA-1501: --- No failures aside from those tracked in KAFKA-2054.

[jira] [Comment Edited] (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=14396022#comment-14396022 ] Gwen Shapira edited comment on KAFKA-1501 at 4/5/15 1:04 AM: -

[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=14396022#comment-14396022 ] Gwen Shapira commented on KAFKA-1501: - Not to take from this awesome improvement, but

[jira] [Commented] (KAFKA-1293) Mirror maker housecleaning

[ https://issues.apache.org/jira/browse/KAFKA-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396007#comment-14396007 ] Matt Warhaftig commented on KAFKA-1293: --- [~jkreps] No, still don't have edit permiss

Build failed in Jenkins: KafkaPreCommit #55

See Changes: [jay.kreps] KAFKA-2024 Log compaction can generate unindexable segments. [jay.kreps] KAFKA-1996 Fix scaladoc error. -- [...truncated 633 lines...] kafka.consumer.ConsumerIteratorTest >

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396005#comment-14396005 ] Sriharsha Chintalapani commented on KAFKA-2082: --- [~junrao] You are right Rep

[jira] [Commented] (KAFKA-1904) run sanity failed test

[ https://issues.apache.org/jira/browse/KAFKA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396003#comment-14396003 ] Gwen Shapira commented on KAFKA-1904: - Depends on whether we are planning to keep syst

Chicken and egg problem when initializing SocketServer

Hi, I'm trying to rebase KAFKA-1809 after KAFKA-1501 was committed, and I'm running into a chicken and egg problem. In my design, SocketServer creates a map of port->SecurityProtocol. This map is passed to Processor when it is initialized, and Processor uses it to route requests to the correct ch

[jira] [Commented] (KAFKA-2078) Getting Selector [WARN] Error in I/O with host java.io.EOFException

[ https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395993#comment-14395993 ] Jun Rao commented on KAFKA-2078: I thought that you were reporting a producer side issue.

[jira] [Resolved] (KAFKA-1996) Scaladoc error: unknown tag parameter

[ https://issues.apache.org/jira/browse/KAFKA-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1996. -- Resolution: Fixed Reviewer: Jay Kreps > Scaladoc error: unknown tag parameter > --

[jira] [Commented] (KAFKA-1293) Mirror maker housecleaning

[ https://issues.apache.org/jira/browse/KAFKA-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395991#comment-14395991 ] Jay Kreps commented on KAFKA-1293: -- [~mwarhaftig] Did we get you wiki access? > Mirror m

Jenkins build is back to normal : KafkaPreCommit #54

See

[jira] [Resolved] (KAFKA-2024) Cleaner can generate unindexable log segments

[ https://issues.apache.org/jira/browse/KAFKA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-2024. -- Resolution: Fixed Reviewer: Jay Kreps Nice catch and nice patch. Applied. > Cleaner can generate

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395985#comment-14395985 ] Jun Rao commented on KAFKA-2082: [~sriharsha], the reason why ReplicaFetcherManager doesn'

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395982#comment-14395982 ] Gwen Shapira commented on KAFKA-1809: - Ick. Looks like KAFKA-1501 was committed. That

[jira] [Commented] (KAFKA-1054) Eliminate Compilation Warnings for 0.8 Final Release

[ https://issues.apache.org/jira/browse/KAFKA-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395980#comment-14395980 ] Jay Kreps commented on KAFKA-1054: -- [~nehanarkhede] I think this is waiting on you. > El

[jira] [Comment Edited] (KAFKA-1528) Normalize all the line endings

[ https://issues.apache.org/jira/browse/KAFKA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395979#comment-14395979 ] Evgeny Vereshchagin edited comment on KAFKA-1528 at 4/4/15 10:41 PM: ---

[jira] [Resolved] (KAFKA-1528) Normalize all the line endings

[ https://issues.apache.org/jira/browse/KAFKA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Vereshchagin resolved KAFKA-1528. Resolution: Not a Problem No. You can close this ticket. > Normalize all the line e

[jira] [Resolved] (KAFKA-1303) metadata request in the new producer can be delayed

[ https://issues.apache.org/jira/browse/KAFKA-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1303. Resolution: Won't Fix I think this is less of an issue given that we have max.in.flight.requests.per.connec

[jira] [Resolved] (KAFKA-2002) It does not work when kafka_mx4jenable is false

[ https://issues.apache.org/jira/browse/KAFKA-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-2002. -- Resolution: Fixed Reviewer: Jay Kreps Assignee: Jay Kreps Nice catch. > It does not work wh

[jira] [Resolved] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-2050. -- Resolution: Fixed Reviewer: Jay Kreps Assignee: Jay Kreps (was: Jun Rao) Nice catch, commit

[jira] [Commented] (KAFKA-1351) String.format is very expensive in Scala

[ https://issues.apache.org/jira/browse/KAFKA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395970#comment-14395970 ] Jay Kreps commented on KAFKA-1351: -- [~nehanarkhede] is this still active? If not can we c

[jira] [Assigned] (KAFKA-2091) Expose a Partitioner interface in the new producer

[ https://issues.apache.org/jira/browse/KAFKA-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-2091: - Assignee: Sriharsha Chintalapani > Expose a Partitioner interface in the

[jira] [Commented] (KAFKA-1904) run sanity failed test

[ https://issues.apache.org/jira/browse/KAFKA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395968#comment-14395968 ] Jay Kreps commented on KAFKA-1904: -- Is this still active? > run sanity failed test > ---

[jira] [Commented] (KAFKA-1528) Normalize all the line endings

[ https://issues.apache.org/jira/browse/KAFKA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395967#comment-14395967 ] Jay Kreps commented on KAFKA-1528: -- [~evvers] is this still active? > Normalize all the

[jira] [Resolved] (KAFKA-312) Add 'reset' operation for AsyncProducerDroppedEvents

[ https://issues.apache.org/jira/browse/KAFKA-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-312. - Resolution: Won't Fix > Add 'reset' operation for AsyncProducerDroppedEvents >

[jira] [Resolved] (KAFKA-1049) Encoder implementations are required to provide an undocumented constructor.

[ https://issues.apache.org/jira/browse/KAFKA-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1049. -- Resolution: Won't Fix Obsolete now that we have the new clients. > Encoder implementations are required

[jira] [Resolved] (KAFKA-1324) Debian packaging

[ https://issues.apache.org/jira/browse/KAFKA-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1324. -- Resolution: Won't Fix I think we can leave packaging out of Kafka itself since this is done in a bunch

[jira] [Resolved] (KAFKA-1956) New consumer client can return early from a poll() call

[ https://issues.apache.org/jira/browse/KAFKA-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1956. -- Resolution: Won't Fix > New consumer client can return early from a poll() call > --

[jira] [Resolved] (KAFKA-530) kafka.server.KafkaApis: kafka.common.OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-530. - Resolution: Won't Fix > kafka.server.KafkaApis: kafka.common.OffsetOutOfRangeException > --

[jira] [Resolved] (KAFKA-552) No error messages logged for those failing-to-send messages from Producer

[ https://issues.apache.org/jira/browse/KAFKA-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-552. - Resolution: Won't Fix > No error messages logged for those failing-to-send messages from Producer > ---

[jira] [Resolved] (KAFKA-777) Add system tests for important tools

[ https://issues.apache.org/jira/browse/KAFKA-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-777. - Resolution: Won't Fix > Add system tests for important tools > > >

[jira] [Resolved] (KAFKA-583) SimpleConsumerShell may receive less data inconsistently

[ https://issues.apache.org/jira/browse/KAFKA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-583. - Resolution: Won't Fix > SimpleConsumerShell may receive less data inconsistently >

[jira] [Resolved] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[ https://issues.apache.org/jira/browse/KAFKA-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1086. -- Resolution: Fixed Assuming this is either fixed or not going to be. > Improve GetOffsetShell to find me

[jira] [Resolved] (KAFKA-1500) adding new consumer requests using the new protocol

[ https://issues.apache.org/jira/browse/KAFKA-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1500. -- Resolution: Fixed > adding new consumer requests using the new protocol > --

[jira] [Updated] (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:all-tabpanel ] Jay Kreps updated KAFKA-1501: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed. [~ewencp] is my personal her

[jira] [Commented] (KAFKA-1303) metadata request in the new producer can be delayed

[ https://issues.apache.org/jira/browse/KAFKA-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395960#comment-14395960 ] Jay Kreps commented on KAFKA-1303: -- [~junrao] What is the status of this? > metadata req

[jira] [Resolved] (KAFKA-1343) Kafka consumer iterator thread stalls

[ https://issues.apache.org/jira/browse/KAFKA-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1343. -- Resolution: Cannot Reproduce > Kafka consumer iterator thread stalls > -

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395959#comment-14395959 ] Jay Kreps commented on KAFKA-1367: -- [~nehanarkhede] Does this problem still exist? > Bro

[jira] [Resolved] (KAFKA-264) Change the consumer side load balancing and distributed co-ordination to use a consumer co-ordinator

[ https://issues.apache.org/jira/browse/KAFKA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-264. - Resolution: Won't Fix I think this is no longer active. > Change the consumer side load balancing and dist

[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=14395955#comment-14395955 ] Jay Kreps commented on KAFKA-1729: -- [~jjkoshy] is this still waiting on an update from yo

[jira] [Resolved] (KAFKA-1728) update 082 docs

[ https://issues.apache.org/jira/browse/KAFKA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1728. -- Resolution: Fixed Closing since it seems like the patch was committed. > update 082 docs >

Re: Review Request 31806: Patch for KAFKA-1501

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31806/#review78892 --- core/src/test/scala/integration/kafka/api/ConsumerTest.scala

Re: Review Request 31806: Patch for KAFKA-1501

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31806/#review78891 --- core/src/test/scala/integration/kafka/api/ConsumerTest.scala

Re: [DISCUSS] New partitioning for better load balancing

Hey guys, I think the first step here would be to expose a partitioner interface for the new producer that would make it easy to plug in these different strategies. I filed a JIRA for this: https://issues.apache.org/jira/browse/KAFKA-2091 -Jay On Fri, Apr 3, 2015 at 9:36 AM, Harsha wrote: > Gi

[jira] [Created] (KAFKA-2091) Expose a Partitioner interface in the new producer

Jay Kreps created KAFKA-2091: Summary: Expose a Partitioner interface in the new producer Key: KAFKA-2091 URL: https://issues.apache.org/jira/browse/KAFKA-2091 Project: Kafka Issue Type: Improvem

Re: [KIP-DISCUSSION] KIP-13 Quotas

Hey Aditya, 2. For the return flag I'm not terribly particular. If we want to add it let's fully think through how it will be used. The only concern I have is adding to the protocol without really thinking through the use cases. So let's work out the APIs we want to add to the Java consumer and pr

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395847#comment-14395847 ] Evan Huus commented on KAFKA-2082: -- Hmm, the test is configured to retry a message 5 time

[jira] [Assigned] (KAFKA-1954) Speed Up The Unit Tests

[ https://issues.apache.org/jira/browse/KAFKA-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned KAFKA-1954: - Assignee: Sriharsha Chintalapani > Speed Up The Unit Tests >