[jira] [Commented] (KAFKA-2172) Round-robin partition assignment strategy too restrictive

[ https://issues.apache.org/jira/browse/KAFKA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533651#comment-14533651 ] Joel Koshy commented on KAFKA-2172: --- The restriction really has to do with simplicity in

[jira] [Commented] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539856#comment-14539856 ] Joel Koshy commented on KAFKA-1374: --- Sorry I dropped this. I just reviewed the patch. I

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539883#comment-14539883 ] Joel Koshy commented on KAFKA-1554: --- That is useful to know - it might help reproducing

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540494#comment-14540494 ] Joel Koshy commented on KAFKA-1554: --- Thanks Steve - sorry I misread your earlier comment

[jira] [Commented] (KAFKA-2186) Follow-up patch of KAFKA-1650

[ https://issues.apache.org/jira/browse/KAFKA-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540706#comment-14540706 ] Joel Koshy commented on KAFKA-2186: --- Hmm.. though this is trivial and an omission from K

[jira] [Updated] (KAFKA-2163) Offsets manager cache should prevent stale-offset-cleanup while an offset load is in progress; otherwise we can lose consumer offsets

[ https://issues.apache.org/jira/browse/KAFKA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2163: -- Resolution: Pending Closed Status: Resolved (was: Patch Available) Committed to trunk. > Offse

[jira] [Updated] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1660: -- Resolution: Pending Closed Status: Resolved (was: Patch Available) Thanks for the patch - commi

[jira] [Updated] (KAFKA-2175) Reduce server log verbosity at info level

[ https://issues.apache.org/jira/browse/KAFKA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2175: -- Resolution: Pending Closed Status: Resolved (was: Patch Available) +1 Thanks for the patch - c

[jira] [Commented] (KAFKA-2160) DelayedOperationPurgatory should remove the pair in watchersForKey with empty watchers list

[ https://issues.apache.org/jira/browse/KAFKA-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546320#comment-14546320 ] Joel Koshy commented on KAFKA-2160: --- I would be surprised if the global RW lock is a pro

[jira] [Updated] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1374: -- Attachment: KAFKA-1374.patch > LogCleaner (compaction) does not support compressed topics >

[jira] [Commented] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549998#comment-14549998 ] Joel Koshy commented on KAFKA-1374: --- Created reviewboard https://reviews.apache.org/r/34

[jira] [Commented] (KAFKA-1778) Create new re-elect controller admin function

[ https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550019#comment-14550019 ] Joel Koshy commented on KAFKA-1778: --- Jun - I think this is more for convenience/debuggin

[jira] [Commented] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551535#comment-14551535 ] Joel Koshy commented on KAFKA-1374: --- Updated reviewboard https://reviews.apache.org/r/34

[jira] [Updated] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1374: -- Attachment: KAFKA-1374_2015-05-19_17:20:44.patch > LogCleaner (compaction) does not support compressed t

[jira] [Resolved] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-1374. --- Resolution: Fixed Please file a separate jira for that. Also, I'm going to amend this commit with the

[jira] [Commented] (KAFKA-1374) LogCleaner (compaction) does not support compressed topics

[ https://issues.apache.org/jira/browse/KAFKA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552840#comment-14552840 ] Joel Koshy commented on KAFKA-1374: --- I just wanted the commit to record Manikumar as aut

[jira] [Created] (KAFKA-2213) Log cleaner should write compacted messages using configured compression type

Joel Koshy created KAFKA-2213: - Summary: Log cleaner should write compacted messages using configured compression type Key: KAFKA-2213 URL: https://issues.apache.org/jira/browse/KAFKA-2213 Project: Kafka

[jira] [Commented] (KAFKA-1778) Create new re-elect controller admin function

[ https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553429#comment-14553429 ] Joel Koshy commented on KAFKA-1778: --- I may be missing some detail, but (a), (b), (c) don

[jira] [Updated] (KAFKA-2186) Follow-up patch of KAFKA-1650

[ https://issues.apache.org/jira/browse/KAFKA-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2186: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - committed to t

[jira] [Updated] (KAFKA-2190) Incorporate close(timeout) to Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2190: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - committed to t

[jira] [Reopened] (KAFKA-2186) Follow-up patch of KAFKA-1650

[ https://issues.apache.org/jira/browse/KAFKA-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy reopened KAFKA-2186: --- Reverted. Reopening due to compilation failure. > Follow-up patch of KAFKA-1650 > ---

[jira] [Commented] (KAFKA-2213) Log cleaner should write compacted messages using configured compression type

[ https://issues.apache.org/jira/browse/KAFKA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559422#comment-14559422 ] Joel Koshy commented on KAFKA-2213: --- Case A: Yes. i.e., if broker compression.type is 'p

[jira] [Updated] (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 ] Joel Koshy updated KAFKA-2091: -- Thanks for the patch - committed to trunk. > Expose a Partitioner interface in the new producer > -

[jira] [Updated] (KAFKA-2186) Follow-up patch of KAFKA-1650

[ https://issues.apache.org/jira/browse/KAFKA-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2186: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - committed to t

[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=14563858#comment-14563858 ] Joel Koshy commented on KAFKA-1367: --- Hi [~singhashish] - sorry I missed your pings. Yes

[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=14563960#comment-14563960 ] Joel Koshy commented on KAFKA-1367: --- Jun - that is a good point. That sounds like a good

[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=14564012#comment-14564012 ] Joel Koshy commented on KAFKA-1367: --- One minor issue with depending on the TMR for KAKFA

[jira] [Updated] (KAFKA-2213) Log cleaner should write compacted messages using configured compression type

[ https://issues.apache.org/jira/browse/KAFKA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2213: -- Reviewer: Joel Koshy > Log cleaner should write compacted messages using configured compression type > -

[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=14569420#comment-14569420 ] Joel Koshy commented on KAFKA-1367: --- You may still want to switch back to a replica in t

[jira] [Created] (KAFKA-2242) Fix license headers (remove copyright notices) in a few test sources

Joel Koshy created KAFKA-2242: - Summary: Fix license headers (remove copyright notices) in a few test sources Key: KAFKA-2242 URL: https://issues.apache.org/jira/browse/KAFKA-2242 Project: Kafka

[jira] [Commented] (KAFKA-2242) Fix license headers (remove copyright notices) in a few test sources

[ https://issues.apache.org/jira/browse/KAFKA-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570230#comment-14570230 ] Joel Koshy commented on KAFKA-2242: --- Thanks - sorry I missed the detail on KAFKA-2161 (e

[jira] [Commented] (KAFKA-2161) Fix a few copyrights

[ https://issues.apache.org/jira/browse/KAFKA-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570235#comment-14570235 ] Joel Koshy commented on KAFKA-2161: --- Pushed to trunk. Ping [~charmalloc] on above commen

[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=14571268#comment-14571268 ] Joel Koshy commented on KAFKA-1367: --- Follow-up from the KIP hangout. Side-note: this and

[jira] [Updated] (KAFKA-2246) UnknownTopicOrPartitionException should be an instance of InvalidMetadataException

[ https://issues.apache.org/jira/browse/KAFKA-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2246: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - pushed to trun

[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=14582433#comment-14582433 ] Joel Koshy commented on KAFKA-1367: --- [~singhashish] - yes that is a good summary. Broker

[jira] [Commented] (KAFKA-2159) offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored

[ https://issues.apache.org/jira/browse/KAFKA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588522#comment-14588522 ] Joel Koshy commented on KAFKA-2159: --- Yes. > offsets.topic.segment.bytes and offsets.top

[jira] [Updated] (KAFKA-2159) offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored

[ https://issues.apache.org/jira/browse/KAFKA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2159: -- Reviewer: Joel Koshy > offsets.topic.segment.bytes and offsets.topic.retention.minutes are ignored > ---

[jira] [Updated] (KAFKA-2213) Log cleaner should write compacted messages using configured compression type

[ https://issues.apache.org/jira/browse/KAFKA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2213: -- Status: In Progress (was: Patch Available) > Log cleaner should write compacted messages using configur

[jira] [Updated] (KAFKA-2245) Add response tests for ConsumerCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2245: -- Resolution: Fixed Reviewer: Joel Koshy Status: Resolved (was: Patch Available) Thanks for

[jira] [Created] (KAFKA-2309) ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR

Joel Koshy created KAFKA-2309: - Summary: ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR Key: KAFKA-2309 URL: https://issues.apache.org/jira/browse/KAFKA-2309 Project: Kafka

[jira] [Updated] (KAFKA-2298) Client Selector can drop connections on InvalidReceiveException without notifying NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2298: -- Reviewer: Joel Koshy > Client Selector can drop connections on InvalidReceiveException without > notify

[jira] [Commented] (KAFKA-2310) Add config to prevent broker becoming controller

[ https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615922#comment-14615922 ] Joel Koshy commented on KAFKA-2310: --- Is this a dup of KAFKA-1778? https://issues.apach

[jira] [Updated] (KAFKA-2298) Client Selector can drop connections on InvalidReceiveException without notifying NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2298: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Client Selector can drop connection

[jira] [Updated] (KAFKA-2241) AbstractFetcherThread.shutdown() should not block on ReadableByteChannel.read(buffer)

[ https://issues.apache.org/jira/browse/KAFKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2241: -- Status: In Progress (was: Patch Available) > AbstractFetcherThread.shutdown() should not block on > Re

[jira] [Commented] (KAFKA-1901) Move Kafka version to be generated in code by build (instead of in manifest)

[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622332#comment-14622332 ] Joel Koshy commented on KAFKA-1901: --- Will review today. > Move Kafka version to be gene

[jira] [Commented] (KAFKA-2275) Add a ListTopics() API to the new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625095#comment-14625095 ] Joel Koshy commented on KAFKA-2275: --- [~onurkaraman] has also been doing some thinking on

[jira] [Commented] (KAFKA-1835) Kafka new producer needs options to make blocking behavior explicit

[ https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627190#comment-14627190 ] Joel Koshy commented on KAFKA-1835: --- bq. Similar proposal applies to KAFKA-2275 https:/

[jira] [Updated] (KAFKA-1901) Move Kafka version to be generated in code by build (instead of in manifest)

[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1901: -- Reviewer: Joel Koshy > Move Kafka version to be generated in code by build (instead of in manifest) > --

[jira] [Commented] (KAFKA-1835) Kafka new producer needs options to make blocking behavior explicit

[ https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627375#comment-14627375 ] Joel Koshy commented on KAFKA-1835: --- bq. I think case (3) is only for users who are will

[jira] [Commented] (KAFKA-1835) Kafka new producer needs options to make blocking behavior explicit

[ https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627474#comment-14627474 ] Joel Koshy commented on KAFKA-1835: --- My earlier comment was more to clarify the reasonin

[jira] [Commented] (KAFKA-1944) Rename LogCleaner and related classes to LogCompactor

[ https://issues.apache.org/jira/browse/KAFKA-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628432#comment-14628432 ] Joel Koshy commented on KAFKA-1944: --- Perhaps KIP would be overkill for this. I would rec

[jira] [Updated] (KAFKA-2336) Changing offsets.topic.num.partitions after the offset topic is created breaks consumer group partition assignment

[ https://issues.apache.org/jira/browse/KAFKA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2336: -- Reviewer: Joel Koshy > Changing offsets.topic.num.partitions after the offset topic is created > breaks

[jira] [Updated] (KAFKA-1901) Move Kafka version to be generated in code by build (instead of in manifest)

[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1901: -- Status: In Progress (was: Patch Available) > Move Kafka version to be generated in code by build (inste

[jira] [Updated] (KAFKA-1911) Log deletion on stopping replicas should be async

[ https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1911: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Log deletion on stopping replicas s

[jira] [Updated] (KAFKA-4250) make ProducerRecord and ConsumerRecord extensible

[ https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-4250: -- Fix Version/s: 0.10.2.0 > make ProducerRecord and ConsumerRecord extensible > --

[jira] [Reopened] (KAFKA-4250) make ProducerRecord and ConsumerRecord extensible

[ https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy reopened KAFKA-4250: --- cc [~becket_qin] [~nsolis] [~radai] > make ProducerRecord and ConsumerRecord extensible > ---

[jira] [Resolved] (KAFKA-4250) make ProducerRecord and ConsumerRecord extensible

[ https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4250. --- Resolution: Fixed > make ProducerRecord and ConsumerRecord extensible > --

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168065#comment-15168065 ] Joel Koshy commented on KAFKA-3197: --- Hi [~fpj] so your suggestion is to preemptively inv

[jira] [Resolved] (KAFKA-3298) Document unclean.leader.election.enable as a valid topic-level config

[ https://issues.apache.org/jira/browse/KAFKA-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-3298. --- Resolution: Duplicate Thanks for the report. KAFKA-3234 addresses this and other such inconsistencies.

[jira] [Updated] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-3197: -- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > Producer can send

[jira] [Updated] (KAFKA-2960) DelayedProduce may cause message loss during repeated leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2960: -- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1018 [

[jira] [Resolved] (KAFKA-1148) Delayed fetch/producer requests should be satisfied on a leader change

[ https://issues.apache.org/jira/browse/KAFKA-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-1148. --- Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1018 [https://github.c

[jira] [Updated] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-3234: -- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > Minor documentation edits: clarify minI

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228733#comment-15228733 ] Joel Koshy commented on KAFKA-3494: --- I'm not sure that the second suggested solution in

[jira] [Commented] (KAFKA-4050) Allow configuration of the PRNG used for SSL

[ https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425906#comment-15425906 ] Joel Koshy commented on KAFKA-4050: --- [~toddpalino] I had left a comment about this on th

[jira] [Resolved] (KAFKA-4050) Allow configuration of the PRNG used for SSL

[ https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4050. --- Resolution: Fixed Fix Version/s: 0.10.0.2 0.10.1.0 Pushed to trunk and 0.10.

[jira] [Created] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

Joel Koshy created KAFKA-4074: - Summary: Deleting a topic can make it unavailable even if delete.topic.enable is false Key: KAFKA-4074 URL: https://issues.apache.org/jira/browse/KAFKA-4074 Project: Kafka

[jira] [Commented] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471686#comment-15471686 ] Joel Koshy commented on KAFKA-4074: --- Yes - totally missed KAFKA-3175 > Deleting a topic

[jira] [Updated] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

[ https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-4158: -- Fix Version/s: 0.10.1.0 > Reset quota to default value if quota override is deleted for a given clientId

[jira] [Resolved] (KAFKA-4158) Reset quota to default value if quota override is deleted for a given clientId

[ https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4158. --- Resolution: Fixed Pushed to trunk. Not sure if we need this in 0.9 since there is an easy work-around

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511604#comment-15511604 ] Joel Koshy commented on KAFKA-4178: --- [~junrao] sorry I don't remember, but you might :)

[jira] [Commented] (KAFKA-4207) Partitions stopped after a rapid restart of a broker

[ https://issues.apache.org/jira/browse/KAFKA-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15524443#comment-15524443 ] Joel Koshy commented on KAFKA-4207: --- I have a KIP draft that has been sitting around for

[jira] [Commented] (KAFKA-4254) Questionable handling of unknown partitions in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553228#comment-15553228 ] Joel Koshy commented on KAFKA-4254: --- It seems (2) would still help as there are use-case

[jira] [Updated] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-3175: -- Resolution: Fixed Reviewer: Joel Koshy Status: Resolved (was: Patch Available) > topic no

[jira] [Updated] (KAFKA-4293) ByteBufferMessageSet.deepIterator burns CPU catching EOFExceptions

[ https://issues.apache.org/jira/browse/KAFKA-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-4293: -- Assignee: radai rosenblatt It turns out we should be able to handle all of our current codecs by re-imp

[jira] [Resolved] (KAFKA-4025) build fails on windows due to rat target output encoding

[ https://issues.apache.org/jira/browse/KAFKA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4025. --- Resolution: Fixed Assignee: radai rosenblatt Reviewer: Joel Koshy Fix Version/

[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=15583851#comment-15583851 ] Joel Koshy commented on KAFKA-1351: --- Yes - this is still an issue. cc [~nsolis] > Strin

[jira] [Resolved] (KAFKA-4250) make ProducerRecord and ConsumerRecord extensible

[ https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-4250. --- Resolution: Fixed Assignee: radai rosenblatt Reviewer: Joel Koshy Fix Version/

[jira] [Created] (KAFKA-4362) Offset commits fail after a partition reassignment

Joel Koshy created KAFKA-4362: - Summary: Offset commits fail after a partition reassignment Key: KAFKA-4362 URL: https://issues.apache.org/jira/browse/KAFKA-4362 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4362) Offset commits fail after a partition reassignment

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624520#comment-15624520 ] Joel Koshy commented on KAFKA-4362: --- Btw, the summary doesn't make it clear that this al

[jira] [Updated] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-4362: -- Summary: Consumer can fail after reassignment of the offsets topic partition (was: Offset commits fail

[jira] [Commented] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645419#comment-15645419 ] Joel Koshy commented on KAFKA-4381: --- This is up to you but I definitely agree with Jason

[jira] [Commented] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645427#comment-15645427 ] Joel Koshy commented on KAFKA-4362: --- Sorry - missed this comment. It does not recover be

[jira] [Commented] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645583#comment-15645583 ] Joel Koshy commented on KAFKA-4362: --- In this specific issue, the coordinator is availabl

[jira] [Created] (KAFKA-4409) ZK consumer shutdown/topic event deadlock

Joel Koshy created KAFKA-4409: - Summary: ZK consumer shutdown/topic event deadlock Key: KAFKA-4409 URL: https://issues.apache.org/jira/browse/KAFKA-4409 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2336) Changing offsets.topic.num.partitions after the offset topic is created breaks consumer group partition assignment

[ https://issues.apache.org/jira/browse/KAFKA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694558#comment-14694558 ] Joel Koshy commented on KAFKA-2336: --- Sorry I should not have assigned it to myself befor

[jira] [Resolved] (KAFKA-2084) byte rate metrics per client ID (producer and consumer)

[ https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2084. --- Resolution: Fixed Thanks for the patches - committed to trunk. > byte rate metrics per client ID (pro

[jira] [Commented] (KAFKA-2084) byte rate metrics per client ID (producer and consumer)

[ https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703921#comment-14703921 ] Joel Koshy commented on KAFKA-2084: --- I pushed a trivial commit to address this. However,

[jira] [Commented] (KAFKA-2084) byte rate metrics per client ID (producer and consumer)

[ https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703965#comment-14703965 ] Joel Koshy commented on KAFKA-2084: --- Actually I did not mean full-fledged [scalastyle|h

[jira] [Resolved] (KAFKA-2446) KAFKA-2205 causes existing Topic config changes to be lost

[ https://issues.apache.org/jira/browse/KAFKA-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2446. --- Resolution: Fixed Pushed to trunk. > KAFKA-2205 causes existing Topic config changes to be lost > ---

[jira] [Updated] (KAFKA-1901) Move Kafka version to be generated in code by build (instead of in manifest)

[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1901: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - committed to t

[jira] [Commented] (KAFKA-2454) Dead lock between delete log segment and shutting down.

[ https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706019#comment-14706019 ] Joel Koshy commented on KAFKA-2454: --- I'm a bit unclear on the root cause that you descri

[jira] [Commented] (KAFKA-2454) Dead lock between delete log segment and shutting down.

[ https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707091#comment-14707091 ] Joel Koshy commented on KAFKA-2454: --- Thanks - got it. Will take a look at your patch tod

[jira] [Updated] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2442: -- Reviewer: Joel Koshy will do > QuotasTest should not fail when cpu is busy > --

[jira] [Updated] (KAFKA-2351) Brokers are having a problem shutting down correctly

[ https://issues.apache.org/jira/browse/KAFKA-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2351: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. > Brokers are ha

[jira] [Commented] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712324#comment-14712324 ] Joel Koshy commented on KAFKA-2136: --- Thanks for the patches - pushed to trunk. Can you u

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2120: -- Status: In Progress (was: Patch Available) > Add a request timeout to NetworkClient > -

[jira] [Updated] (KAFKA-2332) Add quota metrics to old producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2332: -- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) Issue

[jira] [Updated] (KAFKA-2502) Quotas documentation for 0.8.3

[ https://issues.apache.org/jira/browse/KAFKA-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2502: -- Description: Complete quotas documentation Also, https://cwiki.apache.org/confluence/display/KAFKA/A+G

[jira] [Resolved] (KAFKA-2437) Controller does not handle zk node deletion correctly.

[ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2437. --- Resolution: Fixed Fix Version/s: 0.8.3 > Controller does not handle zk node deletion correctly.

<    1   2   3   4   5   6   7   8   9   >