Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi Arun, I was thinking along the same lines as you, listing the use cases on the wiki, but didn't find time to get around doing that yet. Don't mind if you do it if you have access now. I was thinking it would be nice if, once we have the use cases listed, people could use likes to up-vote th

Re: [DISCUSS] KIP-138: Change punctuate semantics

Thanks Michal. I don’t have the access yet [arunmathew88]. Should I be sending a separate mail for this? I thought one of the person following this thread would be able to give me access. From: Michal Borowiecki Reply-To: "dev@kafka.apache.org" Date: Friday, April 7, 2017 at 17:16 To: "dev@kaf

[jira] [Commented] (KAFKA-4967) java.io.EOFException Error while committing offsets

[ https://issues.apache.org/jira/browse/KAFKA-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960489#comment-15960489 ] Upendra Yadav commented on KAFKA-4967: -- Same Exception, even after setting dual.comm

[GitHub] kafka pull request #2821: MINOR: CollectionUtils.groupDataByTopic in Offsets...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2821 MINOR: CollectionUtils.groupDataByTopic in OffsetsForLeaderEpochRequest/Response You can merge this pull request into a Git repository by running: $ git pull https://github.com/benstopfo

[jira] [Created] (KAFKA-5040) Increase number of producer retries from the default of 0

Eno Thereska created KAFKA-5040: --- Summary: Increase number of producer retries from the default of 0 Key: KAFKA-5040 URL: https://issues.apache.org/jira/browse/KAFKA-5040 Project: Kafka Issue T

[jira] [Work started] (KAFKA-5040) Increase number of producer retries from the default of 0

[ https://issues.apache.org/jira/browse/KAFKA-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5040 started by Eno Thereska. --- > Increase number of producer retries from the default of 0 > -

[jira] [Updated] (KAFKA-5040) Increase number of producer retries from the default of 0

[ https://issues.apache.org/jira/browse/KAFKA-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5040: Status: Patch Available (was: In Progress) > Increase number of producer retries from the default o

[GitHub] kafka pull request #2799: Kafka-4990: Add API stubs, config parameters, and ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2799 --- 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] [Updated] (KAFKA-4990) Add request/response classes for transactions (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4990: --- Summary: Add request/response classes for transactions (KIP-98) (was: Add API stubs, config parameter

[jira] [Updated] (KAFKA-4990) Add request/response classes for transactions (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4990: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add request/response classes for

[GitHub] kafka pull request #2821: MINOR: CollectionUtils.groupDataByTopic in Offsets...

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

[GitHub] kafka pull request #2687: KAFKA-4899: Fix findbugs warnings in kafka-core

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2687 --- 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-4899) Fix findbugs warnings in kafka-core

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

[GitHub] kafka pull request #2822: MINOR: Fix incorrect pattern matching on `version`...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2822 MINOR: Fix incorrect pattern matching on `version` in `CheckpointFile` Also add test and refactor things a little to make testing easier. You can merge this pull request into a Git repository by runni

[jira] [Updated] (KAFKA-5036) Followups from KIP-101

[ https://issues.apache.org/jira/browse/KAFKA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5036: --- Description: 1. It would be safer to hold onto the leader lock in Partition while serving an OffsetFo

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi Arun, Could you share your code? Thanks Tianji On Fri, Apr 7, 2017 at 4:21 AM, Arun Mathew wrote: > Thanks Michal. I don’t have the access yet [arunmathew88]. Should I be > sending a separate mail for this? > > I thought one of the person following this thread would be able to give me > acc

[jira] [Updated] (KAFKA-5040) Increase number of producer retries from the default of 0

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

[jira] [Commented] (KAFKA-5040) Increase number of producer retries from the default of 0

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

[GitHub] kafka pull request #2819: KAFKA-5040: Increase number of retries from the de...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2819 --- 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-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960720#comment-15960720 ] Ismael Juma commented on KAFKA-4950: [~vahid], would you like to pick this one up? >

[jira] [Commented] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

[ https://issues.apache.org/jira/browse/KAFKA-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960721#comment-15960721 ] Wim Van Leuven commented on KAFKA-4927: --- What needs to happen to get this PR merged?

[jira] [Updated] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4950: --- Fix Version/s: 0.11.0.0 > ConcurrentModificationException when iterating over Kafka Metrics >

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

See Changes: [ismael] KAFKA-4990; Request/response classes for transactions (KIP-98) -- [...truncated 378.94 KB...] kafka.utils.CommandLineUtilsTest > testParseEmptyArgAs

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960777#comment-15960777 ] Joseph Aliase commented on KAFKA-5007: -- [~junrao][~ijuma] Any help will be appreciate

[jira] [Reopened] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-4825: > Likely Data Loss in ReassignPartitionsTest System Test > -

[jira] [Resolved] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4825. Resolution: Duplicate > Likely Data Loss in ReassignPartitionsTest System Test > ---

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

See Changes: [ismael] MINOR: CollectionUtils.groupDataByTopic in [ismael] KAFKA-4899; Fix findbugs warnings in kafka-core [ismael] KAFKA-5040; Increase number of retries from the default of 0 -

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote updated KAFKA-3955: --- Affects Version/s: 0.10.1.1 > Kafka log recovery doesn't truncate logs on non-monotonic offsets, leadi

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960854#comment-15960854 ] Dustin Cote commented on KAFKA-3955: Adding 0.10.1.1 as this kind of behavior has been

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Labels: reliability (was: ) > Kafka log recovery doesn't truncate logs on non-monotonic offsets, lead

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Fix Version/s: 0.11.0.0 > Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading t

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Priority: Critical (was: Major) > Kafka log recovery doesn't truncate logs on non-monotonic offsets,

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960879#comment-15960879 ] Jun Rao commented on KAFKA-3955: One reason that can cause offsets to go out of order in t

[jira] [Resolved] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3919. Resolution: Fixed Assignee: Ben Stopford Fix Version/s: 0.11.0.0 This is fixed by KAFKA-1211

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

See Changes: [ismael] KAFKA-4990; Request/response classes for transactions (KIP-98) -- [...truncated 942.18 KB...] org.apache.kafka.streams.state.internals.SessionKeySch

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

See

[jira] [Updated] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Aliase updated KAFKA-5007: - Affects Version/s: 0.10.0.0 0.10.2.0 > Kafka Replica Fetcher Thread- Resour

[jira] [Created] (KAFKA-5041) Kafka TestKit library

Ismael Juma created KAFKA-5041: -- Summary: Kafka TestKit library Key: KAFKA-5041 URL: https://issues.apache.org/jira/browse/KAFKA-5041 Project: Kafka Issue Type: New Feature Reporter:

[jira] [Created] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

Tommy Becker created KAFKA-5042: --- Summary: InFlightRequests#isEmpty() always returns false Key: KAFKA-5042 URL: https://issues.apache.org/jira/browse/KAFKA-5042 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961033#comment-15961033 ] Ismael Juma commented on KAFKA-4401: Note that we changed both classes to be abstract

[jira] [Assigned] (KAFKA-5041) Kafka TestKit library

[ https://issues.apache.org/jira/browse/KAFKA-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5041: -- Assignee: Ismael Juma > Kafka TestKit library > - > > Key:

[jira] [Commented] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

[ https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961038#comment-15961038 ] Ismael Juma commented on KAFKA-5042: Great catch. > InFlightRequests#isEmpty() always

[jira] [Updated] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

[ https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5042: --- Fix Version/s: 0.11.0.0 > InFlightRequests#isEmpty() always returns false > --

[jira] [Assigned] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

[ https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5042: -- Assignee: Ismael Juma > InFlightRequests#isEmpty() always returns false > -

[GitHub] kafka pull request #2823: KAFKA-5042: InFlightRequests#isEmpty() always retu...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2823 KAFKA-5042: InFlightRequests#isEmpty() always returns false You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-5042-fix-inflight-r

[jira] [Commented] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

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

[jira] [Commented] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

[ https://issues.apache.org/jira/browse/KAFKA-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961105#comment-15961105 ] Matthias J. Sax commented on KAFKA-4927: I guess, the PR got "forgotten" -- sorry

Re: [DISCUSS] KIP-138: Change punctuate semantics

Arun, I've given you permission to edit the wiki. Let me know if you run into any issues. -Ewen On Fri, Apr 7, 2017 at 1:21 AM, Arun Mathew wrote: > Thanks Michal. I don’t have the access yet [arunmathew88]. Should I be > sending a separate mail for this? > > I thought one of the person follow

[jira] [Updated] (KAFKA-5036) Followups from KIP-101

[ https://issues.apache.org/jira/browse/KAFKA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5036: --- Fix Version/s: 0.11.0.0 > Followups from KIP-101 > -- > > Key: KAF

[jira] [Resolved] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

[ https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-5042. - Resolution: Fixed Issue resolved by pull request 2823 [https://github.com/apache/kafka/pull/2823]

[GitHub] kafka pull request #2823: KAFKA-5042: InFlightRequests#isEmpty() always retu...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2823 --- 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-5042) InFlightRequests#isEmpty() always returns false

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

[jira] [Updated] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

[ https://issues.apache.org/jira/browse/KAFKA-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wim Van Leuven updated KAFKA-4927: -- And? Needs tweaking? > KStreamsTestDriver fails with NPE when KStream.to() sinks are used >

[jira] [Updated] (KAFKA-4901) Make ProduceRequest thread-safe

[ https://issues.apache.org/jira/browse/KAFKA-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4901: Resolution: Fixed Status: Resolved (was: Patch Available) > Make ProduceRequest thread-safe

[jira] [Commented] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

[ https://issues.apache.org/jira/browse/KAFKA-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961152#comment-15961152 ] Matthias J. Sax commented on KAFKA-4927: See Github comments -- just some nitpick.

[GitHub] kafka pull request #2802: MINOR: Log append validation improvements

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2802 --- 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-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961176#comment-15961176 ] Gwen Shapira commented on KAFKA-4814: - Hey guys, I think this is going to be late for

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

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4814: Fix Version/s: (was: 0.10.2.1) > ZookeeperLeaderElector not respecting zookeeper.set.acl > -

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961194#comment-15961194 ] Jun Rao commented on KAFKA-5007: Hmm, ReplicaFetcherThread is changed to use the client se

[GitHub] kafka pull request #2733: KAFKA-4943: Make /config/users with SCRAM credenti...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2733 --- 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-4943) SCRAM secret's should be better protected with Zookeeper ACLs

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

[jira] [Updated] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3758: Resolution: Fixed Status: Resolved (was: Patch Available) > KStream job fails to recover af

[jira] [Updated] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3758: Status: Patch Available (was: Reopened) > KStream job fails to recover after Kafka broker stopped >

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

See Changes: [ismael] MINOR: CollectionUtils.groupDataByTopic in [ismael] KAFKA-4899; Fix findbugs warnings in kafka-core [ismael] KAFKA-5040; Increase number of retries from the default of 0 -

[jira] [Commented] (KAFKA-1019) kafka-preferred-replica-election.sh will fail without clear error message if /brokers/topics/[topic]/partitions does not exist

[ https://issues.apache.org/jira/browse/KAFKA-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961311#comment-15961311 ] Jozef Koval commented on KAFKA-1019: Is it still an issue [~draiwn]? Or can we close t

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961314#comment-15961314 ] Joseph Aliase commented on KAFKA-5007: -- Those leaked sockets don't show up in netstat

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

See

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

See Changes: [cshapi] KAFKA-5042: InFlightRequests#isEmpty() always returns false [ismael] MINOR: Log append validation improvements [cshapi] KAFKA-4943: Make /config/users with SCRAM credentials not world-rea

[jira] [Updated] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

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

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961437#comment-15961437 ] Ismael Juma commented on KAFKA-4943: [~jstrom], can you please file a separate issue a

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961463#comment-15961463 ] Jiangjie Qin commented on KAFKA-4401: - Sure, I just linked KAFKA-5041 to this ticket s

[jira] [Resolved] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4401. - Resolution: Fixed > Change the KafkaServerTestHarness and IntegrationTestHarness from trait to >

[GitHub] kafka pull request #2824: MINOR: Added changes in 0.10.2.1

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2824 MINOR: Added changes in 0.10.2.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka minor-docs-0.10.2.1 Alternatively you ca

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

What about KafkaStreams#toString() method? I think, we want to deprecate it as with KIP-120 and the changes of this KIP, is gets obsolete. If we do so, please update the KIP accordingly. -Matthias On 3/28/17 7:00 PM, Matthias J. Sax wrote: > Thanks for updating the KIP! > > I think it's good

[jira] [Updated] (KAFKA-4876) WindowStore.fetch(key, 0, Long.MaxValue) is very slow

[ https://issues.apache.org/jira/browse/KAFKA-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4876: Fix Version/s: (was: 0.10.2.1) > WindowStore.fetch(key, 0, Long.MaxValue) is very slow > ---

[jira] [Created] (KAFKA-5043) Add FindCoordinatorRequest RPC stub and update InitPidRequest for KIP-98

Apurva Mehta created KAFKA-5043: --- Summary: Add FindCoordinatorRequest RPC stub and update InitPidRequest for KIP-98 Key: KAFKA-5043 URL: https://issues.apache.org/jira/browse/KAFKA-5043 Project: Kafka

[jira] [Created] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

Tommy Becker created KAFKA-5044: --- Summary: max.in.flight.requests.per.connection > 1 is ineffective Key: KAFKA-5044 URL: https://issues.apache.org/jira/browse/KAFKA-5044 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-5043) Add FindCoordinatorRequest RPC stub and update InitPidRequest for KIP-98

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

[GitHub] kafka pull request #2825: KAFKA-5043 : Add FindCoordinatorRPC stub and updat...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2825 KAFKA-5043 : Add FindCoordinatorRPC stub and update InitPidRequest for transactions in KIP-98. You can merge this pull request into a Git repository by running: $ git pull https://github.com/

[GitHub] kafka pull request #2826: Fix KAFKA-5042.

GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/2826 Fix KAFKA-5042. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. You can merge this pull request into a

[jira] [Commented] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

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

[GitHub] kafka pull request #2826: Fix KAFKA-5044.

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

[jira] [Commented] (KAFKA-5042) InFlightRequests#isEmpty() always returns false

[ https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961534#comment-15961534 ] Tommy Becker commented on KAFKA-5042: - Apologies, I used the wrong issue number. Will

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

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

[GitHub] kafka pull request #2827: Fix KAFKA-5044.

GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/2827 Fix KAFKA-5044. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. You can merge this pull request into a

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

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

[GitHub] kafka pull request #2822: MINOR: Fix incorrect pattern matching on `version`...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2822 --- 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-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

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

[GitHub] kafka pull request #2828: KAFKA-5011: down convert the message on replicatio...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2828 KAFKA-5011: down convert the message on replication if necessary You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5011 A

[VOTE] 0.10.2.1 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for the release of Apache Kafka 0.10.2.1. This is a bug fix release and it includes fixes and improvements from 24 JIRAs (including a few critical bugs). See the release notes for more details: http://home.apache.org

[GitHub] kafka pull request #2829: HOTFIX: Use a true sentinel for `UseDefaultAcls`

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2829 HOTFIX: Use a true sentinel for `UseDefaultAcls` In 67fc2a91a6, we are using an empty collection and comparing via value equality, so if a user passes an empty collection, they will get the def

[jira] [Commented] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961626#comment-15961626 ] Jun Rao commented on KAFKA-5011: Yes, this seems to be an issue. However, for this to happ