Build failed in Jenkins: kafka-0.10.0-jdk7 #162

See Changes: [ismael] KAFKA-3933; Always fully read deepIterator [ismael] KAFKA-3935; Fix test_restart_failed_task system test for SinkTasks -- [...truncated 3449 lines...]

Build failed in Jenkins: kafka-trunk-jdk7 #1440

See Changes: [ismael] KAFKA-3933; Always fully read deepIterator [ismael] KAFKA-3935; Fix test_restart_failed_task system test for SinkTasks [ismael] MINOR: cleanup apache license in python files

Build failed in Jenkins: kafka-trunk-jdk8 #775

See Changes: [ismael] KAFKA-3933; Always fully read deepIterator [ismael] KAFKA-3935; Fix test_restart_failed_task system test for SinkTasks [ismael] MINOR: cleanup apache license in python files

[jira] [Updated] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-3989: --- Description: JMH is a Java harness for building, running, and analyzing benchmarks written in Java or

[jira] [Created] (KAFKA-3989) Add JMH module for Benchmarks

Bill Bejeck created KAFKA-3989: -- Summary: Add JMH module for Benchmarks Key: KAFKA-3989 URL: https://issues.apache.org/jira/browse/KAFKA-3989 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393079#comment-15393079 ] Bill Bejeck commented on KAFKA-3973: [~enothereska] Will do, just need to finish up a few details. >

[GitHub] kafka pull request #1659: MINOR: cleanup apache license in python files

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1659 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

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

[jira] [Commented] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

[ https://issues.apache.org/jira/browse/KAFKA-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393047#comment-15393047 ] ASF GitHub Bot commented on KAFKA-3935: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1663: KAFKA-3935: Fix test_restart_failed_task system te...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1663 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3933. Resolution: Fixed Issue resolved by pull request 1660 [https://github.com/apache/kafka/pull/1660]

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393039#comment-15393039 ] ASF GitHub Bot commented on KAFKA-3933: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1660: KAFKA-3933: always fully read deepIterator

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1660 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [DISCUSS] KIP-70: Revise Partition Assignment Semantics on New Consumer's Subscription Change

This is a nice KIP write-up. LGTM too. Guozhang On Fri, Jul 22, 2016 at 12:58 PM, Dana Powers wrote: > This is a nice change. Great KIP write up. > > -Dana > > On Fri, Jul 22, 2016 at 10:07 AM, Vahid S Hashemian > wrote: > > Thanks Ismael. > >

[jira] [Commented] (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:comment-tabpanel=15392910#comment-15392910 ] ASF GitHub Bot commented on KAFKA-1911: --- GitHub user sutambe opened a pull request:

[GitHub] kafka pull request #1664: KAFKA-1911: Async delete topic

GitHub user sutambe opened a pull request: https://github.com/apache/kafka/pull/1664 KAFKA-1911: Async delete topic The last patch submitted by @MayureshGharat (back in Dec 15) has been rebased to the latest trunk. I took care of a couple of test failures (MetricsTest) along the

Re: Can you add me to the contributors?

I have added you as apache id "mailtobuchi" to the list. Guozhang On Wed, Jul 20, 2016 at 6:11 PM, Buchi Reddy Busireddy < mailtobu...@gmail.com> wrote: > Hi awesome Kafka developers, > > I want to contribute to Kafka, starting with fixing a bug. As per the > contribution guidelines, I should

[jira] [Updated] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

[ https://issues.apache.org/jira/browse/KAFKA-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3935: - Status: Patch Available (was: Open) >

[jira] [Commented] (KAFKA-3981) Possible race condition between controller cache and ZK on topic delete

[ https://issues.apache.org/jira/browse/KAFKA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392891#comment-15392891 ] Guozhang Wang commented on KAFKA-3981: -- [~mjsax] Have you figured out the root cause of your observed

[jira] [Commented] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

[ https://issues.apache.org/jira/browse/KAFKA-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392886#comment-15392886 ] ASF GitHub Bot commented on KAFKA-3935: --- GitHub user ewencp opened a pull request:

[GitHub] kafka pull request #1663: KAFKA-3935: Fix test_restart_failed_task system te...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1663 KAFKA-3935: Fix test_restart_failed_task system test for SinkTasks Fix the test by using a more liberal timeout and forcing more frequent SinkTask.put() calls. Also add some logging to aid future

[jira] [Commented] (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:comment-tabpanel=15392877#comment-15392877 ] Sumant Tambe commented on KAFKA-1911: - Hi [~mgharat], I would like to take your patch over. I've

[jira] [Commented] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

[ https://issues.apache.org/jira/browse/KAFKA-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392850#comment-15392850 ] Ewen Cheslack-Postava commented on KAFKA-3935: -- Looked into this a bit more. It looks like

[jira] [Resolved] (KAFKA-3981) Possible race condition between controller cache and ZK on topic delete

[ https://issues.apache.org/jira/browse/KAFKA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3981. Resolution: Not A Problem > Possible race condition between controller cache and ZK on

[jira] [Assigned] (KAFKA-3935) ConnectDistributedTest.test_restart_failed_task.connector_type=sink system test failing

[ https://issues.apache.org/jira/browse/KAFKA-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3935: Assignee: Ewen Cheslack-Postava (was: Jason Gustafson) >

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3500: - Status: Patch Available (was: Open) > KafkaOffsetBackingStore set method needs

[jira] [Commented] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392696#comment-15392696 ] ASF GitHub Bot commented on KAFKA-3500: --- GitHub user ewencp opened a pull request:

[GitHub] kafka pull request #1662: KAFKA-3500: Handle null keys and values in KafkaOf...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1662 KAFKA-3500: Handle null keys and values in KafkaOffsetBackingStore. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka

Build failed in Jenkins: kafka-trunk-jdk8 #774

See Changes: [me] MINOR: Small enhancement to Deserializer Javadoc -- [...truncated 8327 lines...] org.apache.kafka.common.utils.UtilsTest > testGetHost STARTED

[jira] [Assigned] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3500: Assignee: Ewen Cheslack-Postava (was: Liquan Pei) >

[jira] [Commented] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392574#comment-15392574 ] Ewen Cheslack-Postava commented on KAFKA-3500: -- [~liquanpei] Going to grab this since we

Jenkins build is back to normal : kafka-trunk-jdk7 #1439

See

[GitHub] kafka pull request #1503: MINOR: Small enhancement to Deserializer Javadoc

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1503 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3500: - Fix Version/s: (was: 0.10.1.0) 0.10.0.1 >

Re: Can you add me to the contributors?

Buchi, Thanks for your interest. Could you create an Apache account and let us know your id? We can then add you to the contributor list. Jun On Wed, Jul 20, 2016 at 6:11 PM, Buchi Reddy Busireddy < mailtobu...@gmail.com> wrote: > Hi awesome Kafka developers, > > I want to contribute to Kafka,

[jira] [Resolved] (KAFKA-3887) StreamBounceTest.test_bounce and StreamSmokeTest.test_streams failing

[ https://issues.apache.org/jira/browse/KAFKA-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3887. -- Resolution: Fixed > StreamBounceTest.test_bounce and StreamSmokeTest.test_streams failing >

[jira] [Commented] (KAFKA-3887) StreamBounceTest.test_bounce and StreamSmokeTest.test_streams failing

[ https://issues.apache.org/jira/browse/KAFKA-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392273#comment-15392273 ] Guozhang Wang commented on KAFKA-3887: -- Streams system test has been resolved as of KAFKA-3911. >

[jira] [Created] (KAFKA-3988) KafkaConfigBackingStore assumes configs will be stored as schemaless maps

Ewen Cheslack-Postava created KAFKA-3988: Summary: KafkaConfigBackingStore assumes configs will be stored as schemaless maps Key: KAFKA-3988 URL: https://issues.apache.org/jira/browse/KAFKA-3988

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392234#comment-15392234 ] Eno Thereska commented on KAFKA-3973: - [~bbejeck] Thank you for the results. As part of this JIRA I'm

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392083#comment-15392083 ] ASF GitHub Bot commented on KAFKA-3933: --- GitHub user tcrayford reopened a pull request:

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392082#comment-15392082 ] ASF GitHub Bot commented on KAFKA-3933: --- Github user tcrayford closed the pull request at:

[GitHub] kafka pull request #1660: KAFKA-3933: always fully read deepIterator

Github user tcrayford closed the pull request at: https://github.com/apache/kafka/pull/1660 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392037#comment-15392037 ] ASF GitHub Bot commented on KAFKA-3987: --- GitHub user luafran opened a pull request:

[GitHub] kafka pull request #1661: KAFKA-3987: Allow config of the hash algorithm use...

GitHub user luafran opened a pull request: https://github.com/apache/kafka/pull/1661 KAFKA-3987: Allow config of the hash algorithm used by the log cleaner Allow configuration of the hash algorithm used by the Log Cleaner's offset map You can merge this pull request into a Git

[GitHub] kafka pull request #1660: KAFKA-3933: always fully read deepIterator

GitHub user tcrayford opened a pull request: https://github.com/apache/kafka/pull/1660 KAFKA-3933: always fully read deepIterator Avoids leaking native memory and hence crashing brokers on bootup due to running out of memory. Seeeing as `messageFormat > 0` always reads

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391896#comment-15391896 ] ASF GitHub Bot commented on KAFKA-3933: --- GitHub user tcrayford opened a pull request:

[GitHub] kafka pull request #1614: KAFKA-3933: close deepIterator during log recovery

Github user tcrayford closed the pull request at: https://github.com/apache/kafka/pull/1614 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391894#comment-15391894 ] ASF GitHub Bot commented on KAFKA-3933: --- Github user tcrayford closed the pull request at:

[jira] [Updated] (KAFKA-3977) KafkaConsumer swallows exceptions raised from message deserializers

[ https://issues.apache.org/jira/browse/KAFKA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3977: --- Status: Patch Available (was: Open) > KafkaConsumer swallows exceptions raised from message

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391766#comment-15391766 ] Bill Bejeck commented on KAFKA-3973: Yes I ran the tests using instrumentation (-javaagent:), sorry I

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391519#comment-15391519 ] Michael Noll commented on KAFKA-3973: - +1 to having repeatable tests/benchmarks (e.g. with JMH). >

Re: [DISCUSS] KIP-66 Kafka Connect Transformers for messages

API question regarding dead letter queues / sending messages to a null topic in order to get rid of them: I assume we wouldn't suggest users to actually pass `null` into some method, but rather have a proper and descriptive API method such as `discard()` (this name is just an example)? On Sat,

[jira] [Comment Edited] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391502#comment-15391502 ] Ismael Juma edited comment on KAFKA-3973 at 7/25/16 8:01 AM: - Also,

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391502#comment-15391502 ] Ismael Juma commented on KAFKA-3973: Also, MemoryMeasurer has the following enum: {code} public

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391500#comment-15391500 ] Ismael Juma commented on KAFKA-3973: "These benchmarks should be re-written with JMH