[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967026#comment-15967026 ] huxi commented on KAFKA-5062: - I am intrigued by how to reproduce the problem. > Kafka brokers can accept

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967015#comment-15967015 ] James Cheng commented on KAFKA-5062: Sounds like a similar story to

[jira] [Commented] (KAFKA-5049) Chroot check should be done for each ZkUtils instance

[ https://issues.apache.org/jira/browse/KAFKA-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966978#comment-15966978 ] Jun Rao commented on KAFKA-5049: [~ijuma], yes, that does seem to be a problem, [~anukin], if you want to

Re: Credentials for Confluence

It’s simplesteph Thanks for adding me! On 13 April 2017 at 9:28:35 am, Gwen Shapira (g...@confluent.io) wrote: What's your Apache wiki username? On Mon, Apr 10, 2017 at 11:48 PM, Stephane Maarek wrote: > Hi, > > I’d like to create a KIP on Confluence but

[jira] [Created] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

Matthias J. Sax created KAFKA-5063: -- Summary: Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic Key: KAFKA-5063 URL: https://issues.apache.org/jira/browse/KAFKA-5063

[VOTE] 0.10.2.1 RC1

Hello Kafka users, developers, client-developers, friends, romans, citizens, etc, This is the second candidate for release of Apache Kafka 0.10.2.1. This is a bug fix release and it includes fixes and improvements from 24 JIRAs (including a few critical bugs). Release notes for the 0.10.2.1

Re: [VOTE] 0.10.2.1 RC0

Thank you for reporting Eno, and thank you for everyone who tested the release. This is really appreciated. I am rolling out a new RC right now. Expect a new vote thread soon :) On Wed, Apr 12, 2017 at 10:01 AM, Eno Thereska wrote: > Hi Gwen, > > Unfortunately we found

[jira] [Created] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

Apurva Mehta created KAFKA-5062: --- Summary: Kafka brokers can accept malformed requests which allocate gigabytes of memory Key: KAFKA-5062 URL: https://issues.apache.org/jira/browse/KAFKA-5062 Project:

Re: Credentials for Confluence

What's your Apache wiki username? On Mon, Apr 10, 2017 at 11:48 PM, Stephane Maarek wrote: > Hi, > > I’d like to create a KIP on Confluence but according to Matthias Sax I need > credentials. > Can you please provide me some? > > Looking forward to redacting my

[jira] [Commented] (KAFKA-5049) Chroot check should be done for each ZkUtils instance

[ https://issues.apache.org/jira/browse/KAFKA-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966705#comment-15966705 ] anugrah commented on KAFKA-5049: Hey I would like to work on this. Can you pls provide some pointers on

[jira] [Commented] (KAFKA-5059) Implement Transactional Coordinator

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

[GitHub] kafka pull request #2846: KAFKA-5059: Exactly once transactional coordinator

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/2846 --- 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-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966278#comment-15966278 ] Vahid Hashemian commented on KAFKA-5016: [~domenico74] I have not been able to reproduce this

Re: [DISCUSS] KAFKA-4911 Add ProducerRecord to ProducerInterceptor#onAcknowledgement

Does anyone have any thoughts on this? Should I create a proper KIP to better facilitate discussion? On Tue, Mar 21, 2017 at 11:05 AM, Kevin Conaway wrote: > Greetings all, > > Please correct me if this is not the right place to discuss this. I filed > a jira about

[jira] [Updated] (KAFKA-5038) running multiple kafka streams instances causes one or more instance to get into file contention

[ https://issues.apache.org/jira/browse/KAFKA-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5038: Priority: Blocker (was: Major) > running multiple kafka streams instances causes one or more

Re: [VOTE] 0.10.2.1 RC0

Hi Gwen, Unfortunately we found (and just fixed) a bug: https://issues.apache.org/jira/browse/KAFKA-5038 . The PR just went in 0.10.2 and trunk. It'd be great to do another RC since this problem is in the general space of streams lock issues

[jira] [Created] (KAFKA-5061) client.id should be set for Connect producers/consumers

Ewen Cheslack-Postava created KAFKA-5061: Summary: client.id should be set for Connect producers/consumers Key: KAFKA-5061 URL: https://issues.apache.org/jira/browse/KAFKA-5061 Project: Kafka

[jira] [Updated] (KAFKA-5060) Offset not found while broker is rebuilding its index after an index corruption

[ https://issues.apache.org/jira/browse/KAFKA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5060: --- Labels: reliability (was: ) > Offset not found while broker is rebuilding its index after an index

[jira] [Created] (KAFKA-5060) Offset not found while broker is rebuilding its index after an index corruption

Romaric Parmentier created KAFKA-5060: - Summary: Offset not found while broker is rebuilding its index after an index corruption Key: KAFKA-5060 URL: https://issues.apache.org/jira/browse/KAFKA-5060

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

See Changes: [ismael] KAFKA-5038; Throw correct exception of locking of state directory fails -- [...truncated 183.07 KB...] kafka.api.ProducerFailureHandlingTest >

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

See

Re: [VOTE] 0.10.2.1 RC0

Hi Gwen, thanks for the release candidate. Did a quick test, used the RC in my recent project on client side, integration test against server version 0.10.1.1 worked well. +1 (non binding) 2017-04-12 11:31 GMT+02:00 Mickael Maison : > I ran the quickstart steps against

[jira] [Resolved] (KAFKA-5038) running multiple kafka streams instances causes one or more instance to get into file contention

[ https://issues.apache.org/jira/browse/KAFKA-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5038. Resolution: Fixed Fix Version/s: 0.10.2.1 0.11.0.0 Issue resolved by pull

[jira] [Commented] (KAFKA-5038) running multiple kafka streams instances causes one or more instance to get into file contention

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

[GitHub] kafka pull request #2848: KAFKA-5038: Catch exception

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2848 --- 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-5038) running multiple kafka streams instances causes one or more instance to get into file contention

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

[GitHub] kafka pull request #2848: KAFKA-5038: Catch exception

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2848 KAFKA-5038: Catch exception Porting from 0.10.2 PR https://github.com/apache/kafka/pull/2841 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-5038) running multiple kafka streams instances causes one or more instance to get into file contention

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

[GitHub] kafka pull request #2841: KAFKA-5038: Catch exception

Github user enothereska closed the pull request at: https://github.com/apache/kafka/pull/2841 --- 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

[GitHub] kafka pull request #2847: MINOR: update num.x.threads server.properties comm...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/2847 MINOR: update num.x.threads server.properties comments num.io.threads was described as doing disk-IO the description in KafkaConfig is more accurate You can merge this pull request into a

Subscription

Please subscribe for dev news letter. Regards,  -Jaikishan

[jira] [Updated] (KAFKA-5059) Implement Transactional Coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5059: -- Description: This covers the implementation of the transaction coordinator to support transactions, as

[jira] [Created] (KAFKA-5059) Implement Transactional Coordinator

Damian Guy created KAFKA-5059: - Summary: Implement Transactional Coordinator Key: KAFKA-5059 URL: https://issues.apache.org/jira/browse/KAFKA-5059 Project: Kafka Issue Type: New Feature

[GitHub] kafka pull request #2846: [WIP]: Exactly once transactional coordinator

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2846 [WIP]: Exactly once transactional coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/confluentinc/kafka

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

See Changes: [ismael] KAFKA-4965; set internal.leave.group.on.close to false in StreamsConfig -- [...truncated 143.15 KB...]

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

See Changes: [ismael] HOTFIX: HTML formatting error in upgrade docs -- [...truncated 1.54 MB...] kafka.utils.timer.TimerTest > testTaskExpiration PASSED

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

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

[GitHub] kafka pull request #2845: KAFKA-4814: Enable ZK ACLs only when zookeeper.set...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2845 KAFKA-4814: Enable ZK ACLs only when zookeeper.set.acl is set You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965722#comment-15965722 ] Rajini Sivaram commented on KAFKA-4814: --- [~baluchicken] Sorry, I had forgotten about this one. Yes,

[jira] [Commented] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

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

[GitHub] kafka pull request #2750: KAFKA-4965: set internal.leave.group.on.close to f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2750 --- 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-4965) set internal.leave.group.on.close to false in KafkaStreams

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

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

See

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965664#comment-15965664 ] Balint Molnar commented on KAFKA-4814: -- [~rsivaram] I think if we change

[jira] [Comment Edited] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965645#comment-15965645 ] Prakash Gourav edited comment on KAFKA-3450 at 4/12/17 10:19 AM: - What is

[jira] [Comment Edited] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965645#comment-15965645 ] Prakash Gourav edited comment on KAFKA-3450 at 4/12/17 10:18 AM: - What is

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965645#comment-15965645 ] Prakash Gourav commented on KAFKA-3450: --- What is even more sinister is if we call producer.close()

[GitHub] kafka pull request #2844: HOTFIX: HTML formatting error in upgrade docs from...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2844 --- 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-5048) kafka brokers hang when one of broker node killed in the cluster and remaining broker nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965622#comment-15965622 ] huxi commented on KAFKA-5048: - These warnings should be transient as long as you set the replication.factor.

[jira] [Commented] (KAFKA-5057) "Big Message Log"

[ https://issues.apache.org/jira/browse/KAFKA-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965615#comment-15965615 ] Umesh Chaudhary commented on KAFKA-5057: [~gwenshap] currently we have "max.request.size"

Re: [VOTE] 0.10.2.1 RC0

I ran the quickstart steps against the 2.11 binary. Everything worked fine +1 On Wed, Apr 12, 2017 at 8:53 AM, Michal Borowiecki < michal.borowie...@openbet.com> wrote: > FWIW, I upgraded without issue and noticed the speedup from > KAFKA-4851/KAFKA-4876. > > +1 from me (non-binding) > > On

[jira] [Created] (KAFKA-5058) Add a sensor to KafkaStreams to track records that have been dropped due to having a null key

Damian Guy created KAFKA-5058: - Summary: Add a sensor to KafkaStreams to track records that have been dropped due to having a null key Key: KAFKA-5058 URL: https://issues.apache.org/jira/browse/KAFKA-5058

Re: [VOTE] 0.10.2.1 RC0

FWIW, I upgraded without issue and noticed the speedup from KAFKA-4851/KAFKA-4876. +1 from me (non-binding) On 12/04/17 02:06, Gwen Shapira wrote: Wrong link :) http://kafka.apache.org/documentation/#upgrade and http://kafka.apache.org/documentation/streams#streams_api_changes_0102 On Tue,

[jira] [Commented] (KAFKA-5038) running multiple kafka streams instances causes one or more instance to get into file contention

[ https://issues.apache.org/jira/browse/KAFKA-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965448#comment-15965448 ] Bharad Tirumala commented on KAFKA-5038: [~enothereska], I tried the fix and it seems to be

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

See Changes: [ismael] MINOR: Make LeaderAndIsr immutable case class [cshapi] MINOR: Added changes in 0.10.2.1 -- [...truncated 933.49 KB...]