Re: [VOTE] 0.10.2.0 RC0

All, It sounds like https://issues.apache.org/jira/browse/KAFKA-4725 is a regression in an earlier release and worth fixing. I've marked it blocker for 0.10.2.0. I'll plan to roll a new RC once it is committed (some stress testing of the one-line patch is currently ongoing). -Ewen On Fri, Feb

[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

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

[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

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

Re: [VOTE] KIP-109: Old Consumer Deprecation

Sure. The following is the voting outcome. I'll update the KIP too. Voting on this KIP ends with 3 binding and 1 non-binding +1 votes. Thanks to everyone who participated in the discussion / voted on this KIP. The decision was to include it in the release following 0.10.2.0. Binding votes by: *

Re: [VOTE] KIP-109: Old Consumer Deprecation

Thanks. Is it worthwhile updating the KIP with the timeline? So someone like me who is catching up can figure out the status? On Mon, Feb 6, 2017 at 10:08 PM, Vahid S Hashemian wrote: > Hi Gwen, > > The KIP passed with enough binding votes, but I think not everyone was

Re: [VOTE] KIP-109: Old Consumer Deprecation

Hi Gwen, The KIP passed with enough binding votes, but I think not everyone was decided on whether it should go into 0.10.2.0 or the following release. Quoting Ismael on an earlier post in the same thread: {quote} I think there are 2 aspects to this KIP: 1. Deprecating the old consumers 2.

[GitHub] kafka pull request #2510: 0.9.0

GitHub user rajatraj07 opened a pull request: https://github.com/apache/kafka/pull/2510 0.9.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/kafka 0.9.0 Alternatively you can review and apply these changes as the patch

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

It's definitely possible to query an individual group's state efficiently (that's what GroupCoordinator enables). For the group metadata, I wonder if the client should focus on consumer groups rather than exposing the full generality of the group protocol and leaving users to interpret? That would

[jira] [Commented] (KAFKA-4741) Memory leak in RecordAccumulator.append

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

[GitHub] kafka pull request #2509: KAFKA-4741 Fix for buffer leaks in RecordAccumulat...

GitHub user satishd opened a pull request: https://github.com/apache/kafka/pull/2509 KAFKA-4741 Fix for buffer leaks in RecordAccumulator You can merge this pull request into a Git repository by running: $ git pull https://github.com/satishd/kafka buffer-cleanup

[jira] [Created] (KAFKA-4741) Memory leak in RecordAccumulator#append

Satish Duggana created KAFKA-4741: - Summary: Memory leak in RecordAccumulator#append Key: KAFKA-4741 URL: https://issues.apache.org/jira/browse/KAFKA-4741 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4741) Memory leak in RecordAccumulator.append

[ https://issues.apache.org/jira/browse/KAFKA-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated KAFKA-4741: -- Summary: Memory leak in RecordAccumulator.append (was: Memory leak in

Streams: TTLCacheStore

We have a use case within a Streams application that requires a persistent TTL key-value cache store. As Streams does not currently offer such a store, I've implemented it by abusing WindowStore, as it allows for a configurable retention period. Nonetheless, it is not an ideal solution, as you

[jira] [Commented] (KAFKA-4731) Add event-based session windows

[ https://issues.apache.org/jira/browse/KAFKA-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855287#comment-15855287 ] Matthias J. Sax commented on KAFKA-4731: Feel free to take it. I don't see any conflict with the

[DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Two things I want to confirm. Please advise. 1. Seems the KIP only cares about topic management things. Is there any plan for this KIP to merge the feature of what `GetOffsetShell` script offers? Since a lot of people really want to know/monitor how many committed records have been created

Re: [VOTE] KIP-109: Old Consumer Deprecation

What's the status here? It looks like we voted in favor of deprecating in 0.10.2 but the JIRA is open and we rolled out an RC... I'm confused :) On Wed, Jan 11, 2017 at 4:10 PM, Jason Gustafson wrote: > +1 from me. I'm in favor of deprecating in 0.10.2 if possible, or in the

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855232#comment-15855232 ] huxi commented on KAFKA-4739: - Seems that FETCH requests time out every 40 seconds and 40 second is the

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

Hey Jun, Thanks for the review! Please see reply inline. On Mon, Feb 6, 2017 at 6:21 PM, Jun Rao wrote: > Hi, Dong, > > Thanks for the proposal. A few quick questions/comments. > > 1. Do you know why your stress test loses 15% of the throughput with the > one-broker-per-disk

Re: KIP-121 [Discuss]: Add KStream peek method

I've read the wiki and am unclear about the proposal. Can you provide something like a Javadoc for peek()? What would this method do? Also, forgive me if I'm missing an important point here, but can't I put the println statement in a map()? On Mon, Feb 6, 2017 at 5:48 PM, Matthias J. Sax

[jira] [Commented] (KAFKA-4731) Add event-based session windows

[ https://issues.apache.org/jira/browse/KAFKA-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855204#comment-15855204 ] Bill Bejeck commented on KAFKA-4731: [~mjsax] Is this Jira pending any further API redesign

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

even assuming all consumers use kafka for offset storage, would it be possible to get this information from a single broker without "reaching out" to all brokers in a cluster? On Mon, Feb 6, 2017 at 2:05 PM, Jianbin Wei wrote: > In the specify group information, can we

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Sounds good :) On Mon, Feb 6, 2017 at 5:40 PM, Matthias J. Sax wrote: > Gwen, > > thanks for your feedback. > > I completely agree that KStreamBuilder#merge() is miss placed and should > belong to KStream. However, I wanted to keep this KIP focus on one thing. > > As

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

Hi, Dong, Thanks for the proposal. A few quick questions/comments. 1. Do you know why your stress test loses 15% of the throughput with the one-broker-per-disk setup? 2. In the KIP, it wasn't super clear to me what /broker/topics/[topic]/partitions/[partitionId]/controller_managed_state

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hello, I have gone ahead and updated the KIP wiki with a summary of the changes to the RPC protocol. The KIP wiki should now have _all_ the public facing changes being proposed. The proposed changes were always in the Google doc, and now we are simply making good on our promise to copy them over

Re: KIP-121 [Discuss]: Add KStream peek method

Steven, Thanks for your KIP. I move this discussion to dev mailing list -- KIPs need to be discussed there (and can be cc'ed to user list). Can you also add the KIP to the table "KIPs under discussion":

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Gwen, thanks for your feedback. I completely agree that KStreamBuilder#merge() is miss placed and should belong to KStream. However, I wanted to keep this KIP focus on one thing. As mentioned in a previous reply, we plan to have at least one more KIP to clean up DSL -- this future KIP should

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855122#comment-15855122 ] Jason Gustafson commented on KAFKA-4740: That's a good point. We'd have to first return all the

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855098#comment-15855098 ] Jason Gustafson commented on KAFKA-4739: [~sagar8192] Unfortunately, there is no such option.

[jira] [Resolved] (KAFKA-4735) Fix deadlock issue during MM shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4735. - Resolution: Fixed > Fix deadlock issue during MM shutdown > -

[jira] [Updated] (KAFKA-4735) Fix deadlock issue during MM shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4735: Affects Version/s: 0.10.2.0 Fix Version/s: 0.10.3.0 > Fix deadlock issue during MM shutdown

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855052#comment-15855052 ] Vahid Hashemian commented on KAFKA-2857: Sorry, you are right. This would become a config option

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

I like the cleanup a lot :) The cleaner lines between PAPI and DSL are very helpful to beginners who try to make sense of a long list of methods. I noticed that the "merge" method is still part of StreamBuilder. I thought it belongs inside KStream. Merge seems a lot like the SQL "union"

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855034#comment-15855034 ] Jason Gustafson commented on KAFKA-2857: Hmm, I thought we used the admin client for this API.

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

See

[jira] [Commented] (KAFKA-4735) Fix deadlock issue during MM shutdown

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

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hey Tom, Re; complexity. This is always a tradeoff with new features. The changes we've made during the design and review process have greatly simplified the implementation for clients, and especially for the consumer, but there is nontrivial work needed here to support transactions on the

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855001#comment-15855001 ] Vahid Hashemian commented on KAFKA-2857: [~hachikuji] Great. I assume you are suggesting adding a

[GitHub] kafka pull request #2504: KAFKA-4735; Fix deadlock issue during MM shutdown

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

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

See

[jira] [Comment Edited] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854943#comment-15854943 ] Vipul Singh edited comment on KAFKA-4739 at 2/6/17 11:43 PM: - consumer config:

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854869#comment-15854869 ] Jason Gustafson commented on KAFKA-4740: Yeah, auto-commit is the case I was thinking of. I tend

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854956#comment-15854956 ] Sagar Sadashiv Patwardhan commented on KAFKA-4739: -- [~hachikuji] I am with Vipul Singh.

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854943#comment-15854943 ] Vipul Singh commented on KAFKA-4739: consumer config:

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Assigned] (KAFKA-4738) Remove generic type of class ClientState

[ https://issues.apache.org/jira/browse/KAFKA-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharad reassigned KAFKA-4738: - Assignee: Sharad > Remove generic type of class ClientState > >

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854923#comment-15854923 ] Jason Gustafson commented on KAFKA-4739: [~wushujames] Sounds a bit different. Not sure yet, but

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854905#comment-15854905 ] James Cheng commented on KAFKA-4739: I wonder if we're seeing the same thing as this. Kafka 0.9.0.1

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854910#comment-15854910 ] Sébastien Launay commented on KAFKA-4740: - That sounds like a good trade off between ensuring

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi Tom, I updated the KIP with a note our plans for performance testing: https://cwiki.apache.org/confluence/display/KAFKA/KIP-98+-+Exactly+Once+Delivery+and+Transactional+Messaging#KIP-98-ExactlyOnceDeliveryandTransactionalMessaging-Performance Thanks for pointing that out. Regards, Apurva

[GitHub] kafka pull request #2507: HOTFIX: Do Not use unlimited num messages

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2507 --- 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-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854894#comment-15854894 ] Jason Gustafson commented on KAFKA-4739: bq. An observation from our side: it looks like the

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854847#comment-15854847 ] Sébastien Launay commented on KAFKA-4740: - bq. it seems a little riskier since applications which

Build failed in Jenkins: kafka-0.10.2-jdk7 #66

See Changes: [junrao] KAFKA-4441; Monitoring incorrect during topic creation and deletion -- [...truncated 4100 lines...] kafka.api.ProducerFailureHandlingTest > testNotEnoughReplicas STARTED

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854842#comment-15854842 ] Vipul Singh commented on KAFKA-4739: [~hachikuji], I have updated the description of the jira with

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

In the specify group information, can we also return information like partition assignment for each member, the lag/offset of each member/partition? It would be useful for Ops/Admin regarding the health of the consumer group. Regards, -- Jianbin > On Feb 6, 2017, at 13:54, Guozhang Wang

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Some follow-up on 2) / 3) below. On Mon, Feb 6, 2017 at 11:21 AM, Colin McCabe wrote: > On Fri, Feb 3, 2017, at 16:25, Guozhang Wang wrote: > > Thanks for the proposal Colin. A few comments below: > > Thanks for taking a look, Guozhang. > > > > > 1. There are a couple of

[GitHub] kafka pull request #2508: MINOR: Fix import for streams broker compatibility...

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

[GitHub] kafka pull request #2508: MINOR: Fix import for streams broker compatibility...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2508 MINOR: Fix import for streams broker compatibility test to use new DEV_BRANCH constant You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Mathieu, Damian, thanks a lot for your feedback. It's very valuable to see what, how and why people are using certain methods right now. We don't want to lock people out (that's why we put this KIP on users list, too) and we want to keep the ability to mix-and-match DSL and Processor API.

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854791#comment-15854791 ] Jason Gustafson commented on KAFKA-4740: That said, one thing I realized looking at the code is

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854780#comment-15854780 ] Jason Gustafson commented on KAFKA-4740: Thanks for the report. The intention of the current

[jira] [Comment Edited] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854731#comment-15854731 ] Jason Gustafson edited comment on KAFKA-4739 at 2/6/17 9:09 PM:

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854731#comment-15854731 ] Jason Gustafson commented on KAFKA-4739: [~neoeahit] Thanks for the report. Would you mind

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

For individual consumer groups, it would be nice if the admin client made it possible to fetch consumer offsets for the entire consumer group. Then we don't have to manually assemble this outside of the admin client interface. On Feb 6, 2017 11:41 AM, "Colin McCabe" wrote: >

[jira] [Created] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

Sébastien Launay created KAFKA-4740: --- Summary: Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop Key: KAFKA-4740 URL:

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Updated] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Singh updated KAFKA-4739: --- Description: We are seeing an issue with our kafka consumer where it seems to go into an infinite

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854712#comment-15854712 ] Jason Gustafson commented on KAFKA-2857: [~vahid] Sounds reasonable. At least we should have a

[jira] [Created] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

Vipul Singh created KAFKA-4739: -- Summary: KafkaConsumer poll going into an infinite loop Key: KAFKA-4739 URL: https://issues.apache.org/jira/browse/KAFKA-4739 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #2507: HOTFIX: Do Not use unlimited num messages

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2507 HOTFIX: Do Not use unlimited num messages Removed readKeyValues() that give UNLIMITED_MESSAGES which will doom to exhaust all wait time, as all its callers actually do provide the expected

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

> Starting on another host requires restoring from the earliest offset. Btw, there's a special scenario where a full restore is not required: When the local storage (volume) is being re-used, e.g. when a container uses a storage mount that will be re-used by a new container in case the original

[jira] [Resolved] (KAFKA-4441) Kafka Monitoring is incorrect during rapid topic creation and deletion

[ https://issues.apache.org/jira/browse/KAFKA-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4441. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2325

[jira] [Commented] (KAFKA-4441) Kafka Monitoring is incorrect during rapid topic creation and deletion

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

[GitHub] kafka pull request #2325: KAFKA-4441 Monitoring incorrect during topic creat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2325 --- 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-4728) KafkaConsumer#commitSync should clone its input

[ https://issues.apache.org/jira/browse/KAFKA-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4728: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > KafkaConsumer#commitSync

[jira] [Created] (KAFKA-4738) Remove generic type of class ClientState

Matthias J. Sax created KAFKA-4738: -- Summary: Remove generic type of class ClientState Key: KAFKA-4738 URL: https://issues.apache.org/jira/browse/KAFKA-4738 Project: Kafka Issue Type: Bug

Re: Request Wiki edit permission for stevenschlansker

Done. Guozhang On Mon, Feb 6, 2017 at 10:02 AM, Steven Schlansker < stevenschlans...@gmail.com> wrote: > Hi dev@, > > I recently signed up for the Kafka Wiki as 'stevenschlansker' and would > like to contribute a KIP. > May I please have edit access to do so? Thanks! > > -- -- Guozhang

[jira] [Updated] (KAFKA-4728) KafkaConsumer#commitSync should clone its input

[ https://issues.apache.org/jira/browse/KAFKA-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4728: --- Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch

[jira] [Commented] (KAFKA-4728) KafkaConsumer#commitSync should clone its input

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

[GitHub] kafka pull request #2491: [KAFKA-4728] KafkaConsumer#commitSync should clone...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2491 --- 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-117: Add a public AdministrativeClient API for Kafka admin operations

On Fri, Feb 3, 2017, at 16:57, Dong Lin wrote: > Thanks for the reply, Colin. I have some comments inline. Hi Dong L., > > In addition, I also have some comments regarding the Future() in response > to your latest email. As Ismael mentioned, we have added > purgeDataBefore() > API in

[jira] [Commented] (KAFKA-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

[ https://issues.apache.org/jira/browse/KAFKA-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854609#comment-15854609 ] Guozhang Wang commented on KAFKA-4461: -- [~amccague] Thanks for the patch! I have added you to the

[jira] [Resolved] (KAFKA-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

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

[GitHub] kafka pull request #2499: KAFKA-4461 Added support to ProcessorTopologyTestD...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2499 --- 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-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

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

[jira] [Assigned] (KAFKA-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

[ https://issues.apache.org/jira/browse/KAFKA-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4461: Assignee: Adrian McCague > When using ProcessorTopologyTestDriver, the combination of map

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Fri, Feb 3, 2017, at 16:25, Guozhang Wang wrote: > Thanks for the proposal Colin. A few comments below: > > 1. There are a couple of classes that looks new to me but not defined > anywhere. For example: NewTopic (topic name and configs?), TopicInfo (is > this a wrapper of

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Fri, Feb 3, 2017, at 16:25, Guozhang Wang wrote: > Thanks for the proposal Colin. A few comments below: Thanks for taking a look, Guozhang. > > 1. There are a couple of classes that looks new to me but not defined > anywhere. For example: NewTopic (topic name and configs?), TopicInfo (is >

Request Wiki edit permission for stevenschlansker

Hi dev@, I recently signed up for the Kafka Wiki as 'stevenschlansker' and would like to contribute a KIP. May I please have edit access to do so? Thanks! signature.asc Description: Message signed with OpenPGP using GPGMail

[jira] [Commented] (KAFKA-4724) Clean up of state directories can possibly remove stores that are about to be used by another thread

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

[jira] [Resolved] (KAFKA-4724) Clean up of state directories can possibly remove stores that are about to be used by another thread

[ https://issues.apache.org/jira/browse/KAFKA-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4724. -- Resolution: Fixed Issue resolved by pull request 2486

[GitHub] kafka pull request #2486: KAFKA-4724: Clean up of state directories can poss...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2486 --- 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-4555) Using Hamcrest for easy intent expression in tests

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

[GitHub] kafka pull request #2273: KAFKA-4555: Using Hamcrest for expressive intent i...

Github user rekhajoshm closed the pull request at: https://github.com/apache/kafka/pull/2273 --- 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-4264) kafka-server-stop.sh fails is Kafka launched via kafka-server-start.sh

[ https://issues.apache.org/jira/browse/KAFKA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854484#comment-15854484 ] Jeff Maxwell commented on KAFKA-4264: - The pull request

[jira] [Commented] (KAFKA-4564) When the destination brokers are down or misconfigured in config, Streams should fail fast

[ https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854436#comment-15854436 ] Matthias J. Sax commented on KAFKA-4564: With new client compatibility in {{0.10.2}} we did add

[GitHub] kafka-site issue #45: Manual edits needed for 0.10.2 release

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/45 @ewencp @derrickdoo for reviews. --- 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

  1   2   >