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

See Changes: [wangguoz] KAFKA-3994: Fix deadlock in Watchers by calling tryComplete without any -- [...truncated 7994 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

[jira] [Commented] (KAFKA-4486) Kafka Streams - exception in process still commits offsets

[ https://issues.apache.org/jira/browse/KAFKA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723370#comment-15723370 ] Guozhang Wang commented on KAFKA-4486: -- The distinguishment is not in Streams, but in the embedded

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

See Changes: [wangguoz] KAFKA-3994: Fix deadlock in Watchers by calling tryComplete without any -- [...truncated 14446 lines...]

[jira] [Updated] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

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

[VOTE] KIP-88: OffsetFetch Protocol Update

Happy Monday, I'd like to start voting on KIP-88 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-88%3A+OffsetFetch+Protocol+Update ). The discussion thread can be found here: https://www.mail-archive.com/dev@kafka.apache.org/msg59608.html Thank you for your feedback. Regards, --Vahid

Re: [DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

1) The change to consume the metadata topic by all instances should not be big. We want to leverage the "restore consumer" that does manual partitions assignments already. 2) I understand your concern about adding the metadata topic... For a single instance with one thread, it would be easy to go

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

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

[GitHub] kafka pull request #2195: KAFKA-3994: Fix deadlock in Watchers by calling tr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2195 --- 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-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of

[GitHub] kafka pull request #2211: HOTFIX: Fix bug in readToLogEnd in KafkaBasedLog.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2211 --- 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-97: Improved Kafka Client RPC Compatibility Policy

On Fri, Dec 2, 2016, at 13:41, Ashish Singh wrote: > Colin, > > I just rebased KAFKA-3600's PR on trunk. > Thanks, Ashish! > KAFKA-4457 is a good idea, however it is probably doing some redundant > work. AdminClient has a network client that will already have api > versions > info (after

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

See Changes: [me] HOTFIX: Fix bug in readToLogEnd in KafkaBasedLog. -- [...truncated 3899 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testIsrAfterBrokerShutDownAndJoinsBack

[jira] [Created] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

Niranjan Nanda created KAFKA-4489: - Summary: Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections Key: KAFKA-4489 URL: https://issues.apache.org/jira/browse/KAFKA-4489

[jira] [Commented] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723994#comment-15723994 ] huxi commented on KAFKA-4489: - Seems a thread pool holding multiple KafkaConsumer instances was spawned to

[jira] [Commented] (KAFKA-4471) KafkaConsumer unpauses partitions after subscribe()

[ https://issues.apache.org/jira/browse/KAFKA-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724068#comment-15724068 ] Vahid Hashemian commented on KAFKA-4471: [~hachikuji] Thanks for the clarification. [~salaev] I'll

[jira] [Resolved] (KAFKA-4471) KafkaConsumer unpauses partitions after subscribe()

[ https://issues.apache.org/jira/browse/KAFKA-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian resolved KAFKA-4471. Resolution: Not A Bug > KafkaConsumer unpauses partitions after subscribe() >

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

See Changes: [me] HOTFIX: Fix bug in readToLogEnd in KafkaBasedLog. -- [...truncated 12555 lines...] :streams:checkstyleMain :streams:compileTestJavaNote: Some input files use unchecked or

Re: [DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

I'd like to second the discouragement of adding a new topic per job. We went down this path in Samza and I think the result was quite a mess. You had to read the full topic every time a job started and so it added a lot of overhead and polluted the topic space. What if we did the following:

[VOTE] KIP-97: Improved Kafka Client RPC Compatibility Policy

Hi all, I'd like to start voting on KIP-97 (https://cwiki.apache.org/confluence/display/KAFKA/KIP-97%3A+Improved+Kafka+Client+RPC+Compatibility+Policy ). The discussion thread can be found here: https://www.mail-archive.com/dev@kafka.apache.org/msg60955.html Thanks for your feedback. best,

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724000#comment-15724000 ] Jun Rao commented on KAFKA-4454: [~mgharat], I understand the problem that you described. However, I am

[jira] [Assigned] (KAFKA-4480) kafka-configs will execute the removal of an invalid property and not report an error

[ https://issues.apache.org/jira/browse/KAFKA-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4480: -- Assignee: Vahid Hashemian > kafka-configs will execute the removal of an invalid

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724184#comment-15724184 ] huxi commented on KAFKA-2526: - For the new producer, serde config is hard coded as

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

+1 (non-binding). small nit pick - just because you returned a response to user doesnt mean the memory id no longer used. for some cases the actual "point of termination" may be the deserializer (really impl-dependant), but generally, wouldnt it be "nice" to have an explicit dispose() call on

[jira] [Commented] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724538#comment-15724538 ] Ismael Juma commented on KAFKA-4489: You haven't told the consumer to use SSL for the security

[jira] [Comment Edited] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724657#comment-15724657 ] Niranjan Nanda edited comment on KAFKA-4489 at 12/6/16 7:15 AM: Ismael, I

[jira] [Commented] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724308#comment-15724308 ] Niranjan Nanda commented on KAFKA-4489: --- JDK options used: - Version: 1.8 - Heap config: -Xmx4g - GC

[jira] [Commented] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724657#comment-15724657 ] Niranjan Nanda commented on KAFKA-4489: --- Ismael, I understood the issue; the point is why OOM? It's

[jira] [Comment Edited] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724657#comment-15724657 ] Niranjan Nanda edited comment on KAFKA-4489 at 12/6/16 7:13 AM: Ismael, I

[jira] [Comment Edited] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15724308#comment-15724308 ] Niranjan Nanda edited comment on KAFKA-4489 at 12/6/16 4:38 AM: JDK

Re: [DISCUSS] KIP-94: Session Windows

Hi Guozhang, Thanks for the feedback. 1. If we want developers to be able to provide custom SessionStore implementations then we need this method to be on the public interface. We are currently allowing this for other operations, so it seems to make sense, for the sake of consistency, to allow a

[jira] [Updated] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4477: - Attachment: kafka.jstack > Node reduces its ISR to itself, and doesn't

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721875#comment-15721875 ] Michael Andre Pearce (IG) commented on KAFKA-4477: -- This occurred again in a prod

[jira] [Commented] (KAFKA-3951) kafka.common.KafkaStorageException: I/O exception in append to log

[ https://issues.apache.org/jira/browse/KAFKA-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722076#comment-15722076 ] Ismael Juma commented on KAFKA-3951: Is it possible that your `/tmp` folder is being deleted? >

[jira] [Resolved] (KAFKA-3939) add new consumer metrics in docs

[ https://issues.apache.org/jira/browse/KAFKA-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3939. Resolution: Duplicate Will be done as part of KAFKA-3480. > add new consumer metrics in docs >

[jira] [Resolved] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3228. Resolution: Duplicate I think this is the same as KAFKA-4214. Please reopen if you disagree. >

[jira] [Resolved] (KAFKA-2545) SSLConsumerTest.testSeek fails with JDK8u60

[ https://issues.apache.org/jira/browse/KAFKA-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2545. Resolution: Not A Problem Only happens on my laptop (not sure why), so closing. >

[jira] [Resolved] (KAFKA-2540) Inconsistent constant pertaining to autoCommitEnable

[ https://issues.apache.org/jira/browse/KAFKA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2540. Resolution: Won't Fix It's a fair point, but the new consumer has been out for a while and the old

[jira] [Resolved] (KAFKA-2530) metrics for old replica fetcher thread need to be deregistered

[ https://issues.apache.org/jira/browse/KAFKA-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2530. Resolution: Duplicate I believe this is a duplicate of KAFKA-3632. > metrics for old replica

[jira] [Updated] (KAFKA-3944) After the broker restart, fetchers stopped due to a delayed controlled shutdown message

[ https://issues.apache.org/jira/browse/KAFKA-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3944: --- Labels: reliability (was: ) > After the broker restart, fetchers stopped due to a delayed controlled

[jira] [Updated] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3917: --- Labels: reliability (was: ) > Some __consumer_offsets replicas grow way too big >

[jira] [Updated] (KAFKA-3126) Weird behavior in kafkaController on Controlled shutdowns. The leaderAndIsr in zookeeper is not updated during controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3126: --- Labels: reliability (was: ) > Weird behavior in kafkaController on Controlled shutdowns. The

[jira] [Updated] (KAFKA-1833) OfflinePartitionLeaderSelector may return null leader when ISR and Assgined Broker have no common

[ https://issues.apache.org/jira/browse/KAFKA-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1833: --- Labels: easyfix reliability (was: easyfix) > OfflinePartitionLeaderSelector may return null leader

[jira] [Updated] (KAFKA-1106) HighwaterMarkCheckpoint failure puting broker into a bad state

[ https://issues.apache.org/jira/browse/KAFKA-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1106: --- Labels: reliability (was: ) > HighwaterMarkCheckpoint failure puting broker into a bad state >

[jira] [Resolved] (KAFKA-2871) Newly replicated brokers don't expire log segments properly

[ https://issues.apache.org/jira/browse/KAFKA-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2871. Resolution: Duplicate This was changed as part of KIP-33. > Newly replicated brokers don't expire

[jira] [Resolved] (KAFKA-87) time based segment index

[ https://issues.apache.org/jira/browse/KAFKA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-87. -- Resolution: Duplicate Duplicate of KAFKA-3163 > time based segment index > > >

[jira] [Resolved] (KAFKA-746) Snappy compression isn't applied to messages written to disk on broker

[ https://issues.apache.org/jira/browse/KAFKA-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-746. --- Resolution: Fixed I am going to mark this as fixed as there have been no reports of this for several

Re: [VOTE] KIP-96 - Add per partition metrics for in-sync and replica count

Thanks for the KIP, +1 (binding). Ismael On Thu, Dec 1, 2016 at 12:59 PM, Tom Crayford wrote: > +1 (non-binding) > > On Thu, Dec 1, 2016 at 12:11 AM, Apurva Mehta wrote: > > > +1 (non-binding) > > > > On Wed, Nov 30, 2016 at 2:00 PM, Jason Gustafson

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1907: --- Labels: reliability zkclient-problems (was: zkclient-problems) > ZkClient can block controlled

[jira] [Updated] (KAFKA-740) Improve crash-safety of log segment swap

[ https://issues.apache.org/jira/browse/KAFKA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-740: -- Labels: reliability (was: ) > Improve crash-safety of log segment swap >

Re: [DISCUSS] KIP-96 - Add per partition metrics for in-sync and assigned replica count

Hi Gwen, At this level, that's probably right, so sounds good (at an implementor's level, I think it's more subtle). Ismael On Fri, Dec 2, 2016 at 8:51 PM, Gwen Shapira wrote: > All replicas are assigned replicas. Calling it AssignedReplicasCount > makes it sound like we

[jira] [Updated] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3940: --- Labels: newbie reliability (was: newbie) > Log should check the return value of dir.mkdirs() >

[jira] [Updated] (KAFKA-3900) High CPU util on broker

[ https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3900: --- Labels: reliability (was: ) > High CPU util on broker > --- > >

[jira] [Commented] (KAFKA-3900) High CPU util on broker

[ https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722088#comment-15722088 ] Ismael Juma commented on KAFKA-3900: Does this still happen with 0.10.1.0? There was a fix in the code

[jira] [Updated] (KAFKA-3240) Replication issues

[ https://issues.apache.org/jira/browse/KAFKA-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3240: --- Labels: reliability (was: ) > Replication issues > -- > > Key:

[jira] [Updated] (KAFKA-3033) Reassigning partition stuck in progress

[ https://issues.apache.org/jira/browse/KAFKA-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3033: --- Labels: reliability (was: ) > Reassigning partition stuck in progress >

[jira] [Resolved] (KAFKA-2627) Kafka Heap Size increase impact performance badly

[ https://issues.apache.org/jira/browse/KAFKA-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2627. Resolution: Not A Problem As stated, this is a GC tuning issue and not a Kafka issue. > Kafka Heap

[jira] [Resolved] (KAFKA-2303) Fix for KAFKA-2235 LogCleaner offset map overflow causes another compaction failures

[ https://issues.apache.org/jira/browse/KAFKA-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2303. Resolution: Duplicate I think this is a duplicate of KAFKA-3894. Please reopen if you disagree. >

[jira] [Updated] (KAFKA-2158) Close all fetchers in AbstractFetcherManager without blocking

[ https://issues.apache.org/jira/browse/KAFKA-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2158: --- Resolution: Duplicate Status: Resolved (was: Patch Available) Duplicate of KAFKA-4319. >

[GitHub] kafka pull request #2211: HOTFIX: Fix bug in readToLogEnd in KafkaBasedLog.

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/2211 HOTFIX: Fix bug in readToLogEnd in KafkaBasedLog. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafka

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

> On Dec 2, 2016, at 4:57 PM, Michael Pearce wrote: > > Hi Jun. > > RE Mirroring, > > [...] > > Lastly around mirroring we have a partionKey field, as the key used for > portioning logic != compaction key all the time but we want to preserve it > for when we mirror

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

Hi James, Yes exactly what we do. Alas as it's bespoke to our internal wrapper ATM so we cannot share this. This is the eco system argument that's with having native headers then we would be able to share these kind of things. Cheers Mike Sent using OWA for iPhone

[jira] [Updated] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Olson updated KAFKA-3228: Fix Version/s: 0.10.1.0 > Partition reassignment failure for brokers freshly added to cluster >

Re: [VOTE] KIP-96 - Add per partition metrics for in-sync and replica count

+1 > On Nov 30, 2016, at 4:34 PM, Xavier Léauté wrote: > > Based on the feedback KIP-96 seems pretty uncontroversial, so I'd like to > initiate a vote on it. > >

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

+1 (non binding) -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6

[jira] [Commented] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722341#comment-15722341 ] Andrew Olson commented on KAFKA-3228: - Since the exception message that we saw has been removed from

[jira] [Commented] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722343#comment-15722343 ] Andrew Olson commented on KAFKA-3228: - Added fix version and duplicate link. > Partition reassignment

[jira] [Updated] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3228: --- Fix Version/s: (was: 0.10.1.0) > Partition reassignment failure for brokers freshly added to

[jira] [Commented] (KAFKA-3228) Partition reassignment failure for brokers freshly added to cluster

[ https://issues.apache.org/jira/browse/KAFKA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722362#comment-15722362 ] Ismael Juma commented on KAFKA-3228: Thanks for confirming. I removed the fix version to avoid having

Re: [VOTE] KIP-96 - Add per partition metrics for in-sync and replica count

+1 On Mon, Dec 5, 2016 at 8:07 AM, Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > Ismael > > On Thu, Dec 1, 2016 at 12:59 PM, Tom Crayford > wrote: > > > +1 (non-binding) > > > > On Thu, Dec 1, 2016 at 12:11 AM, Apurva Mehta

[VOTE] KIP-81: Bound Fetch memory usage in the consumer

Hi all, I'd like to start the vote for KIP-81: https://cwiki.apache.org/confluence/display/KAFKA/KIP-81%3A+Bound+Fetch+memory+usage+in+the+consumer Thank you

[jira] [Work started] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3811 started by Eno Thereska. --- > Introduce Kafka Streams metrics recording levels >

[jira] [Assigned] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3811: --- Assignee: Eno Thereska (was: aarti gupta) > Introduce Kafka Streams metrics recording

[jira] [Commented] (KAFKA-4486) Kafka Streams - exception in process still commits offsets

[ https://issues.apache.org/jira/browse/KAFKA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722633#comment-15722633 ] Joel Lundell commented on KAFKA-4486: - [~guozhang], I'm throwing a

[jira] [Comment Edited] (KAFKA-4486) Kafka Streams - exception in process still commits offsets

[ https://issues.apache.org/jira/browse/KAFKA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722715#comment-15722715 ] Joel Lundell edited comment on KAFKA-4486 at 12/5/16 4:48 PM: -- I debugged a

[jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722752#comment-15722752 ] Eno Thereska commented on KAFKA-3811: - This JIRA will be resolved as part of

[jira] [Resolved] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-3811. - Resolution: Duplicate https://issues.apache.org/jira/browse/KAFKA-3715 > Introduce Kafka Streams

[jira] [Work started] (KAFKA-4488) UnsupportedOperationException during initialization of StandbyTask

[ https://issues.apache.org/jira/browse/KAFKA-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4488 started by Damian Guy. - > UnsupportedOperationException during initialization of StandbyTask >

[jira] [Created] (KAFKA-4488) UnsupportedOperationException during initialization of StandbyTask

Damian Guy created KAFKA-4488: - Summary: UnsupportedOperationException during initialization of StandbyTask Key: KAFKA-4488 URL: https://issues.apache.org/jira/browse/KAFKA-4488 Project: Kafka

[jira] [Commented] (KAFKA-4488) UnsupportedOperationException during initialization of StandbyTask

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

[GitHub] kafka pull request #2212: KAFKA-4488: UnsupportedOperationException during i...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2212 KAFKA-4488: UnsupportedOperationException during initialization of StandbyTask Instead of throwing `UnsupportedOperationException` from `StandbyTask.recordCollector()` return a No-op implementation