[jira] [Created] (KAFKA-4865) 2X8BF

Vamsi Jakkula created KAFKA-4865: Summary: 2X8BF Key: KAFKA-4865 URL: https://issues.apache.org/jira/browse/KAFKA-4865 Project: Kafka Issue Type: Bug Reporter: Vamsi Jakkula Cre

Re: [VOTE] KIP-128: Add ByteArrayConverter for Kafka Connect

+1. Looks good On Tue, Mar 7, 2017 at 10:33 PM, Ewen Cheslack-Postava wrote: > Hah, I forgot to do it in the original email, but I suppose I should make > it explicit: +1 (binding) > > -Ewen > > On Mon, Mar 6, 2017 at 9:26 PM, Gwen Shapira wrote: > > > +1 (binding) > > > > On Mon, Mar 6, 2017 a

Re: [VOTE] KIP-128: Add ByteArrayConverter for Kafka Connect

Hah, I forgot to do it in the original email, but I suppose I should make it explicit: +1 (binding) -Ewen On Mon, Mar 6, 2017 at 9:26 PM, Gwen Shapira wrote: > +1 (binding) > > On Mon, Mar 6, 2017 at 7:53 PM, Ewen Cheslack-Postava > wrote: > > > Hi all, > > > > I'd like to kick off voting for

[GitHub] kafka pull request #2655: KAFKA-4864 added correct zookeeper nodes for secur...

GitHub user simplesteph opened a pull request: https://github.com/apache/kafka/pull/2655 KAFKA-4864 added correct zookeeper nodes for security migrator You can merge this pull request into a Git repository by running: $ git pull https://github.com/simplesteph/kafka fix-securit

[jira] [Commented] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900780#comment-15900780 ] ASF GitHub Bot commented on KAFKA-4864: --- GitHub user simplesteph opened a pull reque

[jira] [Updated] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-4864: --- Description: It seems that the secure nodes as referred by ZkUtils.scala are the following: h

[jira] [Updated] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-4864: --- Priority: Critical (was: Major) > Kafka Secure Migrator tool doesn't secure all the nodes > -

[jira] [Created] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

Stephane Maarek created KAFKA-4864: -- Summary: Kafka Secure Migrator tool doesn't secure all the nodes Key: KAFKA-4864 URL: https://issues.apache.org/jira/browse/KAFKA-4864 Project: Kafka Iss

[jira] [Assigned] (KAFKA-4863) Querying window store may return unwanted keys

[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4863: Assignee: Eno Thereska > Querying window store may return unwanted keys > -

[GitHub] kafka-site pull request #50: Typo in kafka 0.10.2 topics operation doc

GitHub user jlisam13 opened a pull request: https://github.com/apache/kafka-site/pull/50 Typo in kafka 0.10.2 topics operation doc I believe it should be "not" and not "noi" You can merge this pull request into a Git repository by running: $ git pull https://github.com/jlisam13

[jira] [Updated] (KAFKA-4863) Querying window store may return unwanted keys

[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4863: - Affects Version/s: 0.10.2.0 > Querying window store may return unwanted keys > ---

[jira] [Updated] (KAFKA-4863) Querying window store may return unwanted keys

[ https://issues.apache.org/jira/browse/KAFKA-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4863: - Description: Using variable length keys in a window store may cause unwanted results to be return

[jira] [Created] (KAFKA-4863) Querying window store may return unwanted keys

Xavier Léauté created KAFKA-4863: Summary: Querying window store may return unwanted keys Key: KAFKA-4863 URL: https://issues.apache.org/jira/browse/KAFKA-4863 Project: Kafka Issue Type: Bug

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

See

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

See Changes: [ismael] KAFKA-4841; NetworkClient should only consider a connection to have -- [...truncated 918.89 KB...] org.apache.kafka.connect.runtime.WorkerSinkTaskThr

[jira] [Created] (KAFKA-4862) Kafka client connect to a shutdown node will block for a long time

Pengwei created KAFKA-4862: -- Summary: Kafka client connect to a shutdown node will block for a long time Key: KAFKA-4862 URL: https://issues.apache.org/jira/browse/KAFKA-4862 Project: Kafka Issue T

[GitHub] kafka pull request #2654: KAFKA-3989_follow_up PR: update script to run from...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/2654 KAFKA-3989_follow_up PR: update script to run from kafka root eg ./jm… …h-benchmarks/jmh.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/b

Re: [DISCUSS] KIP-82 - Add Record Headers

just to clarify - ListIterator is a nice API, and doesnt constrain the implementation a lot more than Iterator (especially if we implement previous() very inefficiently :-) ), but changing Iterable headers(String key) into ListIterator headers(String key) would lose us the ability to easily write w

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

Damian, Jun, Thanks for your input. About Performance test: I can follow up with more performance tests using more partitions and also collecting broker metrics. However, I want to highlight again, that even if 1000+ partitions would be problematic, one can simply implement PartitionGrouper in

[jira] [Updated] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

[ https://issues.apache.org/jira/browse/KAFKA-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4841: --- Fix Version/s: 0.11.0.0 > NetworkClient should only consider a connection to be fail after attempt to

[jira] [Resolved] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

[ https://issues.apache.org/jira/browse/KAFKA-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4841. Resolution: Fixed > NetworkClient should only consider a connection to be fail after attempt to > c

Jenkins build is back to normal : kafka-0.10.2-jdk7 #98

See

[GitHub] kafka pull request #2641: KAFKA-4841; NetworkClient should only consider a c...

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

[jira] [Commented] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

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

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

See Changes: [wangguoz] KAFKA-4851: only search available segments during -- [...truncated 156.93 KB...] kafka.security.auth.SimpleAclAuthorizerTest > testLoadCache START

Re: [DISCUSS] KIP-124: Request rate quotas

I’ve been following this one on and off, and overall it sounds good to me. - The SSL question is a good one. However, that type of overhead should be proportional to the bytes rate, so I think that a bytes rate quota would still be a suitable way to address it. - I think it’s better to make the q

[jira] [Comment Edited] (KAFKA-3795) Transient system test failure upgrade_test.TestUpgrade

[ https://issues.apache.org/jira/browse/KAFKA-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900450#comment-15900450 ] Apurva Mehta edited comment on KAFKA-3795 at 3/8/17 12:28 AM: --

[jira] [Commented] (KAFKA-3795) Transient system test failure upgrade_test.TestUpgrade

[ https://issues.apache.org/jira/browse/KAFKA-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900450#comment-15900450 ] Apurva Mehta commented on KAFKA-3795: - Another instance: https://testbreak.confluent.i

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

Thanks to everyone who voted and/or provided feedback. +1 from me too. The vote passed with 6 binding +1s (Guozhang, Ewen, Gwen, Grant, Becket, Ismael) and 9 non-binding +1s (Dongjin, Molnar, Tom, Eno, Bill, Jozef, Apurva, Dong, Mickael). I will update the relevant wiki pages. Ismael On Tue, Fe

[jira] [Assigned] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4858: -- Assignee: Vahid Hashemian > Long topic names created using old kafka-topics.sh can prev

[GitHub] kafka pull request #2653: MINOR: Update possible errors in OffsetFetchRespon...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2653 MINOR: Update possible errors in OffsetFetchResponse Note: None of the use cases for offset fetch would lead to a `TOPIC_AUTHORIZATION_FAILED` error (fetching offset of an unauthorized parti

[jira] [Resolved] (KAFKA-4851) SessionStore.fetch(key) is a performance bottleneck

[ https://issues.apache.org/jira/browse/KAFKA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4851. -- Resolution: Fixed Fix Version/s: 0.10.2.1 Issue resolved by pull request 2645 [https://gi

[jira] [Commented] (KAFKA-4851) SessionStore.fetch(key) is a performance bottleneck

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

[GitHub] kafka pull request #2645: KAFKA-4851: only search available segments during ...

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

Re: [DISCUSS] KIP-124: Request rate quotas

I see. Good point about SSL. I just asked Todd to take a look. Thanks, Jiangjie (Becket) Qin On Tue, Mar 7, 2017 at 2:17 PM, Jun Rao wrote: > Hi, Jiangjie, > > Yes, I agree that byte rate already protects the network threads > indirectly. I am not sure if byte rate fully captures the CPU over

Re: [DISCUSS] KIP-124: Request rate quotas

Hi, Jiangjie, Yes, I agree that byte rate already protects the network threads indirectly. I am not sure if byte rate fully captures the CPU overhead in network due to SSL. So, at the high level, we can use request time limit to protect CPU and use byte rate to protect storage and network. Also,

[jira] [Commented] (KAFKA-4795) Confusion around topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900271#comment-15900271 ] Vahid Hashemian commented on KAFKA-4795: [~ijuma] [~hachikuji] I'd appreciate your

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Becket, Thanks for the review. 1. I have thought about this before. I think it is fine to delete the node after controller reads it. On controller failover, the new controller will always send LeaderAndIsrRequest for all partitions to each broker in order to learn about offline replicas. 2.

[DISCUSS] KIP-131 : Add access to OffsetStorageReader from SourceConnector

Hi all, I've created a new KIP to add access to OffsetStorageReader from SourceConnector https://cwiki.apache.org/confluence/display/KAFKA/KIP-131+-+Add+access+to+OffsetStorageReader+from+SourceConnector Thanks. -- Florian HUSSONNOIS

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi Dong, Thanks for the KIP, a few more comments: 1. In the KIP wiki section "A log directory stops working on a broker during runtime", the controller deletes the notification node right after it reads the znode. It seems safer to do this at last so even though the controller fails the new contr

[jira] [Updated] (KAFKA-4861) log.message.timestamp.type=LogAppendTime breaks Kafka based consumers

[ https://issues.apache.org/jira/browse/KAFKA-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4861: --- Fix Version/s: 0.10.2.1 > log.message.timestamp.type=LogAppendTime breaks Kafka based consumer

Re: [DISCUSS] KIP-82 - Add Record Headers

where do you see insert-in-the-middle/replace being commonly used? lineage tracing, as you call it, would probably be implemented by way of: 1. every "stop" along the way appending itself (at the end) 2. some replication technologies, instead of just doing #1, may clear out everything when they re

[jira] [Created] (KAFKA-4861) log.message.timestamp.type=LogAppendTime breaks Kafka based consumers

Dustin Cote created KAFKA-4861: -- Summary: log.message.timestamp.type=LogAppendTime breaks Kafka based consumers Key: KAFKA-4861 URL: https://issues.apache.org/jira/browse/KAFKA-4861 Project: Kafka

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Ismael, Thanks much for taking time to review the KIP and read through all the discussion! Please see my reply inline. On Tue, Mar 7, 2017 at 9:47 AM, Ismael Juma wrote: > Hi Dong, > > It took me a while, but I finally went through the whole thread. I have a > few minor comments: > > 1. Re

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi Jun, Ismael, I think making the API similar to a future KIP is desirable but not required. Implementation is easy but discussion of the API may take a lot of time given that we haven't yet reached agreement on KIP-117. Thus I prefer to just mark the API in Scala as unstable. I am OK with eithe

Re: [DISCUSS] KIP-124: Request rate quotas

Hi Rajini/Jun, The percentage based reasoning sounds good. One thing I am wondering is that if we assume the network thread are just doing the network IO, can we say bytes rate quota is already sort of network threads quota? If we take network threads into the consideration here, would that be som

[jira] [Updated] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

[ https://issues.apache.org/jira/browse/KAFKA-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4859: --- Component/s: streams > Transient test failure: > org.apache.kafka.streams.integration.JoinInt

Re: [DISCUSS] KIP-124: Request rate quotas

Jun, Thank you for the explanation, I hadn't realized you meant percentage of the total thread pool. If everyone is OK with Jun's suggestion, I will update the KIP. Thanks, Rajini On Tue, Mar 7, 2017 at 5:08 PM, Jun Rao wrote: > Hi, Rajini, > > Let's take your example. Let's say a user sets t

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi, Dong, Ismael, 1. I just meant that it would be useful to distinguish between removing the whole log vs removing a portion of the log. The exact naming is less important. 4. When we move the purgeBefore() api to the Java AdminClient, it would be great if the api looks comparable to what's in K

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899847#comment-15899847 ] Edoardo Comar commented on KAFKA-4669: -- [~ijuma] It's the same NPE as https://issues

[jira] [Commented] (KAFKA-4844) kafka is holding open file descriptors

[ https://issues.apache.org/jira/browse/KAFKA-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899848#comment-15899848 ] Colin P. McCabe commented on KAFKA-4844: http://nfs.sourceforge.net/#faq_d2 bq. D

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Hi Dong, Thanks for the comments. The patch is mostly for proof of concept in case there is any concern about the implementation which is indeed a little tricky. The new metric has already been mentioned in the Public Interface Change section. I added the reasoning about how the compression rat

[jira] [Commented] (KAFKA-4566) Can't Symlink to Kafka bins

[ https://issues.apache.org/jira/browse/KAFKA-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899843#comment-15899843 ] Colin P. McCabe commented on KAFKA-4566: bq. I know this is a bit more than intend

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899835#comment-15899835 ] Ismael Juma commented on KAFKA-4669: It seems plausible that if that NPE happens, we p

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899832#comment-15899832 ] Ismael Juma commented on KAFKA-4669: That NPE looks like KAFKA-3689. > KafkaProducer.

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi Dong, It took me a while, but I finally went through the whole thread. I have a few minor comments: 1. Regarding the metrics, can we include the full name (e.g. kafka.cluster:type=Partition,name=InSyncReplicasCount, topic={topic},partition={partition} was defined in KIP-96)? 2. We talk about

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899827#comment-15899827 ] Edoardo Comar commented on KAFKA-4669: -- We have found a strong correlation between th

[jira] [Commented] (KAFKA-4437) Incremental Batch Processing for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899823#comment-15899823 ] Matthias J. Sax commented on KAFKA-4437: Kafka 0.10.2 got released already not con

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

Hi, Guozhang, Thanks for the KIP. A couple of comments. 1. About the impact on producer batching. My understanding is that typically different sub-topologies in the same task are publishing to different topics. Since the producer batching happens at the topic/partition level, using a producer per

Re: [DISCUSS] KIP-124: Request rate quotas

Hi, Rajini, Let's take your example. Let's say a user sets the limit to 50%. I am not sure if it's better to apply the same percentage separately to network and io thread pool. For example, for produce requests, most of the time will be spent in the io threads whereas for fetch requests, most of t

[GitHub] kafka pull request #2652: MINOR: add warning when offset topic is not replic...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2652 MINOR: add warning when offset topic is not replicated properly Added a warning, otherwise this problem is hard to debug if you haven't followed the latest KIP closely. You can merge this pull

[jira] [Commented] (KAFKA-4849) Bug in KafkaStreams documentation

[ https://issues.apache.org/jira/browse/KAFKA-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899743#comment-15899743 ] Matthias J. Sax commented on KAFKA-4849: [~habdank] Your Jira description says: "2

[jira] [Assigned] (KAFKA-4857) Improve Client handling

[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharad reassigned KAFKA-4857: - Assignee: Sharad > Improve Client handling > --- > > Key: KAFKA-4857

[jira] [Resolved] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian resolved KAFKA-4845. Resolution: Duplicate > KafkaConsumer.seekToEnd cannot take effect when integrating with spa

[jira] [Commented] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899634#comment-15899634 ] Vahid Hashemian commented on KAFKA-4845: Great, then I'll mark this one as a dupli

Re: Wiki edit permission

Thanks, Guozhang:) 2017-03-07 16:03 GMT+01:00 Guozhang Wang : > Done. > > Cheers, > Guozhang > > On Tue, Mar 7, 2017 at 2:59 AM, Molnár Bálint > wrote: > > > Just a kindly remainder. > > > > Thanks, > > Balint > > > > 2017-03-03 8:44 GMT+01:00 Molnár Bálint : > > > > > Hi, > > > > > > I would li

Re: Wiki edit permission

Done. Cheers, Guozhang On Tue, Mar 7, 2017 at 2:59 AM, Molnár Bálint wrote: > Just a kindly remainder. > > Thanks, > Balint > > 2017-03-03 8:44 GMT+01:00 Molnár Bálint : > > > Hi, > > > > I would like to create a KIP, please add create permission to the wiki > > page. > > My username is baluchi

[jira] [Updated] (KAFKA-4657) Improve test coverage of CompositeReadOnlyWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4657: -- Description: No tests that cover what happens when {{windowStore.fetch(...)}} throw an {{InvalidStateSt

[jira] [Commented] (KAFKA-4437) Incremental Batch Processing for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899518#comment-15899518 ] Ritesh Agarwal commented on KAFKA-4437: --- Dear Team, Could you please let us know re

[GitHub] kafka pull request #2651: MINOR: reduce() javadocs: clarify position of argu...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2651 MINOR: reduce() javadocs: clarify position of arguments You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka trunk-reduce-javadocs Alter

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

Hi Matthias, Thanks. The perf test is a good start but I don't think it goes far enough. 100 partitions is not a lot. What happens when there are thousands of partitions? What is the load on the brokers? How much more memory is used by the Streams App etc? Thanks, Damian On Tue, 7 Mar 2017 at 03

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899306#comment-15899306 ] Dan commented on KAFKA-4834: No. I found in another broker's log that it changed the same part

[jira] [Commented] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899299#comment-15899299 ] Dan commented on KAFKA-4845: I checked 0.10.2.0 again and it was indeed fixed. Thanks a lot!

[GitHub] kafka pull request #2650: [WIP]: add internal leave.group.on.close config to...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2650 [WIP]: add internal leave.group.on.close config to consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/dguy/kafka consumer-leave-group-config

Re: Wiki edit permission

Just a kindly remainder. Thanks, Balint 2017-03-03 8:44 GMT+01:00 Molnár Bálint : > Hi, > > I would like to create a KIP, please add create permission to the wiki > page. > My username is baluchicken. > > Thanks >

[GitHub] kafka pull request #2627: [WIP]: add a consumer leave group config

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

Re: Allow to replace Zookeeper with different Coordination Service (etcd/consul)

Thanks, for pointing me to the right direction:). I will take a look on this KIP. 2017-03-06 16:48 GMT+01:00 Ofir Manor : > I suggest you check KIP-30 and the extensive discussion about it in the > mailing list from around December 2015 called "[DISCUSS] KIP-30 Allow for > brokers to have plug-a