Kafka 0.11.0.1 and filebeat 6.1 compatibility

Hi All, I am using filebeat 6.1 and kafka 0.11.0.1 to push logs. From filebeat logs I could see that communication is getting established but then logs are not getting pushed. Also when I updated filebeat's output.kafka.version to 0.11.0.1 I get error message : 2018/02/08

zstd support status

Hello, I'm very interested in having zstd support in Kafka. There's a ticket, a KIP and even a PR: * https://issues.apache.org/jira/browse/KAFKA-4514 * https://cwiki.apache.org/confluence/display/KAFKA/KIP-110%3A+Add+Codec+for+ZStandard+Compression * https://github.com/apache/kafka/pull/2267

Jenkins build is back to normal : kafka-trunk-jdk8 #2404

See

Build failed in Jenkins: kafka-trunk-jdk9 #387

See Changes: [me] KAFKA-6513: Corrected how Converters and HeaderConverters are -- [...truncated 1.47 MB...] kafka.zk.KafkaZkClientTest > testBrokerSequenceIdMethods

Re: Getting started with contributions

Hi Matthias, my jira id is adityavivek94. On Sat, Feb 10, 2018 at 3:24 AM, Matthias J. Sax wrote: > Can your share your JIRA id, so we can add you to the list of > contributors? This allows you to assign Jiras to yourself. > > > -Matthias > > On 2/9/18 12:34 PM, Aditya

Jenkins build is back to normal : kafka-trunk-jdk9 #386

See

Re: [VOTE] 1.0.1 RC0

Just a heads up that we had a fix for KAFKA-6529 land to fix a file descriptor leak. So this RC is dead and I'll be generating RC1 soon. Thanks, Ewen On Wed, Feb 7, 2018 at 11:06 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi Ewen, > > +1 > > Building from source and running the

[jira] [Resolved] (KAFKA-6513) New Connect header support doesn't define `converter.type` property correctly

[ https://issues.apache.org/jira/browse/KAFKA-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6513. -- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request

Re: Getting started with contributions

Can your share your JIRA id, so we can add you to the list of contributors? This allows you to assign Jiras to yourself. -Matthias On 2/9/18 12:34 PM, Aditya Vivek wrote: > Hi team, > > I've followed the instructions given here >

Getting started with contributions

Hi team, I've followed the instructions given here https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes and forked the main repo. How do I go about getting added to the contributor list and picking up one of the starter jiras linked on the how to contribute page? Thanks,

Question about developer documentation

There is some documentation for developers at:   http://kafka.apache.org/project There's also another set of links at the bottom of this wiki page:   https://cwiki.apache.org/confluence/display/KAFKA/Index There's some minor duplication of information, but it's definitely not quite presented

Jenkins build is back to normal : kafka-0.11.0-jdk7 #355

See

[jira] [Resolved] (KAFKA-6407) Sink task metrics are the same for all connectors

[ https://issues.apache.org/jira/browse/KAFKA-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Yokota resolved KAFKA-6407. -- Resolution: Duplicate > Sink task metrics are the same for all connectors >

[jira] [Resolved] (KAFKA-4632) Kafka Connect WorkerSinkTask.closePartitions doesn't handle WakeupException

[ https://issues.apache.org/jira/browse/KAFKA-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4632. -- Resolution: Fixed Fix Version/s: 0.10.0.1 0.10.1.0 I'm going to close

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

See Changes: [rajinisivaram] KAFKA-6529: Stop file descriptor leak when client disconnects with -- [...truncated 413.02 KB...]

Build failed in Jenkins: kafka-trunk-jdk9 #385

See Changes: [rajinisivaram] KAFKA-6529: Stop file descriptor leak when client disconnects with -- [...truncated 1.69 MB...] at

RE: [DISCUSS]KIP-235 DNS alias and secured connections

Hi, I have raised a PR https://github.com/apache/kafka/pull/4485 with suggested code changes. There are however reported failures, don't understand what's the issue since tests are passing. Any ideas ? Jonathan Skrzypek -Original Message- From: Skrzypek, Jonathan [Tech] Sent: 29

Re: [VOTE] KIP-251: Allow timestamp manipulation in Processor API

Thanks for the KIP, +1 for me. -Bill On Fri, Feb 9, 2018 at 6:45 AM, Damian Guy wrote: > Thanks Matthias, +1 > > On Fri, 9 Feb 2018 at 02:42 Ted Yu wrote: > > > +1 > > Original message From: "Matthias J. Sax" < > >

[jira] [Created] (KAFKA-6551) Unbounded queues in WorkerSourceTask cause OutOfMemoryError

Gunnar Morling created KAFKA-6551: - Summary: Unbounded queues in WorkerSourceTask cause OutOfMemoryError Key: KAFKA-6551 URL: https://issues.apache.org/jira/browse/KAFKA-6551 Project: Kafka

[jira] [Created] (KAFKA-6550) UpdateMetadataRequest should be lazily created

huxihx created KAFKA-6550: - Summary: UpdateMetadataRequest should be lazily created Key: KAFKA-6550 URL: https://issues.apache.org/jira/browse/KAFKA-6550 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-251: Allow timestamp manipulation in Processor API

Thanks Matthias, +1 On Fri, 9 Feb 2018 at 02:42 Ted Yu wrote: > +1 > Original message From: "Matthias J. Sax" < > matth...@confluent.io> Date: 2/8/18 6:05 PM (GMT-08:00) To: > dev@kafka.apache.org Subject: [VOTE] KIP-251: Allow timestamp > manipulation in

[jira] [Resolved] (KAFKA-6548) Migrate committed offsets from ZooKeeper to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-6548. - Resolution: Not A Problem Hi [~ppmanikandan...@gmail.com]  it sounds like in principle you know

[jira] [Created] (KAFKA-6549) Deadlock in ZookeeperClient while processing Controller Events

Manikumar created KAFKA-6549: Summary: Deadlock in ZookeeperClient while processing Controller Events Key: KAFKA-6549 URL: https://issues.apache.org/jira/browse/KAFKA-6549 Project: Kafka Issue