[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&focusedCommentId=15678587#comment-15678587 ] Jiangjie Qin commented on KAFKA-3994: - [~mjuarez] Thanks for the update. Good to know.

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

See Changes: [ismael] KAFKA-4420; Group StopReplicaRequests for partitions on the same broker -- [...truncated 14380 lines...] org.apache.kafka.streams.KafkaStreamsTest > shouldNotGetTaskWithK

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

See Changes: [ismael] KAFKA-4420; Group StopReplicaRequests for partitions on the same broker -- [...truncated 14359 lines...] org.apache.kafka.streams.processor.internals.StreamsMetadataStateTe

[jira] [Updated] (KAFKA-3866) KerberosLogin refresh time bug and other improvements

[ https://issues.apache.org/jira/browse/KAFKA-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3866: --- Fix Version/s: (was: 0.10.1.1) 0.10.2.0 > KerberosLogin refresh time bug and ot

[jira] [Updated] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4362: --- Fix Version/s: 0.10.1.1 > Consumer can fail after reassignment of the offsets topic partition > --

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4399: --- Fix Version/s: 0.10.1.1 > Deadlock between cleanupGroupMetadata and offset commit > --

[jira] [Resolved] (KAFKA-4420) Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest

[ https://issues.apache.org/jira/browse/KAFKA-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4420. Resolution: Fixed > Group StopReplicaRequests for partitions on the same broker into one > StopRepl

[jira] [Updated] (KAFKA-4420) Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest

[ https://issues.apache.org/jira/browse/KAFKA-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4420: --- Fix Version/s: 0.10.2.0 > Group StopReplicaRequests for partitions on the same broker into one > Stop

[jira] [Updated] (KAFKA-4420) Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest

[ https://issues.apache.org/jira/browse/KAFKA-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4420: --- Issue Type: Improvement (was: Bug) > Group StopReplicaRequests for partitions on the same broker into

[jira] [Commented] (KAFKA-4420) Group StopReplicaRequests for partitions on the same broker into one StopReplicaRequest

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

[GitHub] kafka pull request #2148: KAFKA-4420; Group StopReplicaRequests for partitio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2148 --- 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-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&focusedCommentId=15678062#comment-15678062 ] mjuarez commented on KAFKA-3994: Turns out I was wrong. The deadlock we saw in our kafka

[jira] [Comment Edited] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677990#comment-15677990 ] Damian Guy edited comment on KAFKA-4270 at 11/18/16 10:41 PM: --

[jira] [Commented] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677990#comment-15677990 ] Damian Guy commented on KAFKA-4270: --- Hi Mykola, I'm not entirely sure i follow what you

[jira] [Updated] (KAFKA-4416) Add a '--group' option to the console consumer

[ https://issues.apache.org/jira/browse/KAFKA-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4416: --- Status: Patch Available (was: Open) > Add a '--group' option to the console consumer > --

Re: [DISCUSS] Deprecating the old consumers in trunk

So my earlier stated suboptimal migration plans and Joel's idea all suffer from either downtime or dual partition ownership and consumption. But I think there's a bigger problem: they assume users are willing to do the full migration immediately. I'm not convinced that this is realistic. Some team

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi, Radai, 3. Having a gauge of MemoryAvailable is useful. One issue with that though is that if one only collects the metrics say every minute, one doesn't know what has happened in between. We could additionally track the fraction of the time when requested memory can't be served. Every time a r

[GitHub] kafka pull request #2147: revert corrupted commit 10cfc1628df024f7596d3af5c1...

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

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

Summary: 3) Yes - Header value as byte[] 4a) Int,Int - No 4b) Int - Yes 4c) String - Reluctant maybe 5) I believe the header system should take a single int. I think 32bits is a good size, if you want to interpret this as to 16bit numbers in the layer above go right ahead. If somebody wants to

[DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

Hi all, I want to start a discussion about KIP-93: https://cwiki.apache.org/confluence/display/KAFKA/KIP-93%3A+Improve+invalid+timestamp+handling+in+Kafka+Streams Looking forward to your feedback. -Matthias signature.asc Description: OpenPGP digital signature

[jira] [Commented] (KAFKA-4416) Add a '--group' option to the console consumer

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

[GitHub] kafka pull request #2150: KAFKA-4416: Add a `--group` option to console cons...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2150 KAFKA-4416: Add a `--group` option to console consumer The value provided for this option overwrites any `group.id` value indirectly provided via `consumer-property` or `consumer.config` opti

[jira] [Assigned] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4270: - Assignee: Damian Guy > ClassCast for Agregation > > > Ke

[jira] [Commented] (KAFKA-4373) Kafka Consumer API jumping offsets

[ https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677456#comment-15677456 ] Guozhang Wang commented on KAFKA-4373: -- This may be resulted from the intermediate to

[jira] [Assigned] (KAFKA-3701) Expose KafkaStreams metrics in public API

[ https://issues.apache.org/jira/browse/KAFKA-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitch Seymour reassigned KAFKA-3701: Assignee: Mitch Seymour > Expose KafkaStreams metrics in public API > -

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

#jay #jun any concerns on 1 and 2 still? @all To get this moving along a bit more I'd also like to ask to get clarity on the below last points: 3) I believe we're all roughly happy with the header value being a byte[]? 4) I believe consensus has been for an namespace based int approach {int,int

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

See Changes: [ismael] KAFKA-4377; remove deprecated scala.collection.JavaConversions calls -- [...truncated 14207 lines...] org.apache.kafka.streams.kstream.JoinWindowsTest > beforeOverUpper STA

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi Michael, That whilst sending tombstone and non null value, the consumer can expect only to receive the non-null message only in step (3) is this correct? ---> I do agree with you here. Becket, Ismael : can you guys review the migration plan listed above using magic byte? Thanks, Mayuresh On

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Many thanks for this Mayuresh. I don't have any objections. I assume we should state: That whilst sending tombstone and non null value, the consumer can expect only to receive the non-null message only in step (3) is this correct? Cheers Mike Sent using OWA for iPhone ___

[jira] [Comment Edited] (KAFKA-4373) Kafka Consumer API jumping offsets

[ https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677107#comment-15677107 ] Conor Hughes edited comment on KAFKA-4373 at 11/18/16 4:42 PM: -

[jira] [Commented] (KAFKA-4373) Kafka Consumer API jumping offsets

[ https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677107#comment-15677107 ] Conor Hughes commented on KAFKA-4373: - I have experienced a similar issue using Kafka

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi Jun, 3. will (also :-) ) do. do you have ideas for appropriate names/metrics? I'm thinking along the lines of "MemoryAvailable" (current snapshot value from pool) and "Throttles" (some moving-avg of how often does throttling due to no mem kicks in). maybe also "BuffersOutstanding" ? On Thu, No

[jira] [Created] (KAFKA-4423) Drop support for Java 7

Ismael Juma created KAFKA-4423: -- Summary: Drop support for Java 7 Key: KAFKA-4423 URL: https://issues.apache.org/jira/browse/KAFKA-4423 Project: Kafka Issue Type: Task Reporter: Isma

[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10

[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Issue Type: Task (was: Bug) > Drop support for Scala 2.10 > --- > >

[jira] [Created] (KAFKA-4422) Drop support for Scala 2.10

Ismael Juma created KAFKA-4422: -- Summary: Drop support for Scala 2.10 Key: KAFKA-4422 URL: https://issues.apache.org/jira/browse/KAFKA-4422 Project: Kafka Issue Type: Bug Reporter: I

[GitHub] kafka pull request #2149: HOTFIX: Hotfix streams smoke test

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2149 HOTFIX: Hotfix streams smoke test You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka hotfix-streams-smoke-test Alternatively

[jira] [Created] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

Ismael Juma created KAFKA-4421: -- Summary: Update release process so that Scala 2.12 artifacts are published Key: KAFKA-4421 URL: https://issues.apache.org/jira/browse/KAFKA-4421 Project: Kafka

[jira] [Resolved] (KAFKA-4377) Remove deprecated scala.collection.JavaConversions

[ https://issues.apache.org/jira/browse/KAFKA-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4377. Resolution: Fixed > Remove deprecated scala.collection.JavaConversions > ---

[jira] [Updated] (KAFKA-4377) Remove deprecated scala.collection.JavaConversions

[ https://issues.apache.org/jira/browse/KAFKA-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4377: --- Summary: Remove deprecated scala.collection.JavaConversions (was: Address 2.12 deprecations) > Remov

[jira] [Updated] (KAFKA-4377) Remove deprecated scala.collection.JavaConversions

[ https://issues.apache.org/jira/browse/KAFKA-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4377: --- Fix Version/s: 0.10.2.0 > Remove deprecated scala.collection.JavaConversions > ---

[jira] [Updated] (KAFKA-4377) Remove deprecated scala.collection.JavaConversions

[ https://issues.apache.org/jira/browse/KAFKA-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4377: --- Assignee: Bernard Leach > Remove deprecated scala.collection.JavaConversions > ---

[jira] [Commented] (KAFKA-4377) Address 2.12 deprecations

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

[GitHub] kafka pull request #2101: KAFKA-4377: remove deprecated scala.collection.Jav...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2101 --- 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-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted

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

[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted

[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676555#comment-15676555 ] ASF GitHub Bot commented on KAFKA-4355: --- GitHub user enothereska reopened a pull req

[GitHub] kafka pull request #2133: KAFKA-4355: Skip topics that have no partitions

GitHub user enothereska reopened a pull request: https://github.com/apache/kafka/pull/2133 KAFKA-4355: Skip topics that have no partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-4355-topic-not-fou

[GitHub] kafka pull request #2133: KAFKA-4355: Skip topics that have no partitions

Github user enothereska closed the pull request at: https://github.com/apache/kafka/pull/2133 --- 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-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676418#comment-15676418 ] Yiquan Zhou commented on KAFKA-4391: I did some tests with 0.10.1.0, I still got the s

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

For what it is worth also i agree. As a user: 1) Yes - Headers are worthwhile 2) Yes - Headers should be a top level option 14.11.2016, 21:15, "Ignacio Solis" : > 1) Yes - Headers are worthwhile > 2) Yes - Headers should be a top level option > > On Mon, Nov 14, 2016 at 9:16 AM, Michael Pearce