[jira] [Commented] (KAFKA-4164) Kafka produces excessive logs when publishing message to non-existent topic

[ https://issues.apache.org/jira/browse/KAFKA-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495450#comment-15495450 ] Manikumar Reddy commented on KAFKA-4164: This is a valid concern. Currently metadata

[jira] [Updated] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1464: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1776

[GitHub] kafka pull request #1776: KIP-73 - Replication Quotas

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1776 --- 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] [Issue Comment Deleted] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4126: --- Comment: was deleted (was: Yes. Another issue related to producer excessive warn logging is

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495420#comment-15495420 ] Manikumar Reddy commented on KAFKA-4126: Yes. Another issue related to producer excessive warn

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495422#comment-15495422 ] Manikumar Reddy commented on KAFKA-4126: Yes. Another issue related to producer excessive warn

[jira] [Assigned] (KAFKA-2700) delete topic should remove the corresponding ACL and configs

[ https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-2700: -- Assignee: Manikumar Reddy (was: Parth Brahmbhatt) > delete topic should remove the

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

See Changes: [wangguoz] KAFKA-4131; Multiple Regex KStream-Consumers cause Null pointer -- [...truncated 3507 lines...] kafka.security.auth.OperationTest > testFromString PASSED

Jenkins build is back to normal : kafka-trunk-jdk7 #1542

See

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

The only pending update for the KIP is to write up the protocol changes like we've it KIP-4. I'll update the wiki. On Thu, Sep 15, 2016 at 4:27 PM Ashish Singh wrote: > I think we decided to not support secret rotation, I guess this can be > stated clearly on the KIP. Also,

[jira] [Commented] (KAFKA-4131) Multiple Regex KStream-Consumers cause Null pointer exception in addRawRecords in RecordQueue class

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

[GitHub] kafka pull request #1843: KAFKA-4131 :Multiple Regex KStream-Consumers cause...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1843 --- 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-4131) Multiple Regex KStream-Consumers cause Null pointer exception in addRawRecords in RecordQueue class

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

[jira] [Updated] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4126: --- Status: Patch Available (was: Open) > No relevant log when the topic is non-existent >

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

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

[GitHub] kafka pull request #1863: KAFKA-4126: Log a server-side warning when a recor...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1863 KAFKA-4126: Log a server-side warning when a record is sent to a missing topic with auto create disabled You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

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

[GitHub] kafka pull request #1863: KAFKA-4126: Log a server-side warning when a recor...

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

[GitHub] kafka pull request #1863: Log a server-side warning when a record is sent to...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1863 Log a server-side warning when a record is sent to a missing topic with auto create disabled You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

I think we decided to not support secret rotation, I guess this can be stated clearly on the KIP. Also, more details on how clients will perform token distribution and how CLI will look like will be helpful. On Thu, Sep 15, 2016 at 3:20 PM, Gwen Shapira wrote: > Hi Guys, > >

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

According to the meeting minutes of KIP hangout on 8/30, it seems the KIP wiki needs some update? KIP48 (delegation tokens): Harsha will update the wiki with more details on how to use delegation tokens and how to configure it. Not sure if that has been done or not. On Thu, Sep 15, 2016 at 3:20

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Hi Guys, This discussion was dead for a while. Are there still contentious points? If not, why are there no votes? On Tue, Aug 23, 2016 at 1:26 PM, Jun Rao wrote: > Ashish, > > Yes, I will send out a KIP invite for next week to discuss KIP-48 and other > remaining KIPs. > >

[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78

[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Description: Add documentation to include details on Cluster Id in "Implementation" section.

[jira] [Updated] (KAFKA-4151) Update public docs for KIP-78

[ https://issues.apache.org/jira/browse/KAFKA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Arrawatia updated KAFKA-4151: --- Summary: Update public docs for KIP-78 (was: System tests for KIP-78 ) > Update public docs

[jira] [Commented] (KAFKA-4126) No relevant log when the topic is non-existent

[ https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494627#comment-15494627 ] Vahid Hashemian commented on KAFKA-4126: [~omkreddy] Do you also get repeating log messages (like

[jira] [Commented] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494596#comment-15494596 ] Jiangjie Qin commented on KAFKA-1464: - It seems the PR title did not start with "KAFKA-1464" so the PR

[jira] [Work started] (KAFKA-3856) Move inner classes accessible only functions in TopologyBuilder out of public APIs

[ https://issues.apache.org/jira/browse/KAFKA-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3856 started by Jeyhun Karimov. - > Move inner classes accessible only functions in TopologyBuilder out of

[jira] [Updated] (KAFKA-3825) Allow users to specify different types of state stores in Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov updated KAFKA-3825: -- Status: Patch Available (was: Open) > Allow users to specify different types of state stores

[jira] [Commented] (KAFKA-3825) Allow users to specify different types of state stores in Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494574#comment-15494574 ] Jeyhun Karimov commented on KAFKA-3825: --- I am closing this issue as the PR has already been

[jira] [Updated] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov updated KAFKA-3184: -- Assignee: Guozhang Wang (was: Jeyhun Karimov) > Add Checkpoint for In-memory State Store >

[jira] [Updated] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov updated KAFKA-3184: -- Assignee: (was: Guozhang Wang) > Add Checkpoint for In-memory State Store >

Re: [VOTE] KIP-54: Sticky Partition Assignment Strategy

+1 On Thu, Sep 15, 2016 at 5:16 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > +1 (non-binding) > > On Wed, Sep 14, 2016 at 12:37 AM, Jason Gustafson > wrote: > > > Thanks for the KIP. +1 from me. > > > > On Tue, Sep 13, 2016 at 12:05 PM, Vahid S Hashemian < > >

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

See Changes: [wangguoz] HOTFIX: fix KafkaStreams SmokeTest -- [...truncated 10897 lines...] org.apache.kafka.clients.consumer.KafkaConsumerTest > testSubscriptionOnEmptyTopic PASSED

Build failed in Jenkins: kafka-0.10.0-jdk7 #200

See Changes: [wangguoz] HOTFIX: set sourceNodes to null for selectKey -- [...truncated 5757 lines...] org.apache.kafka.streams.kstream.internals.KTableSourceTest > testKTable PASSED

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

See Changes: [wangguoz] HOTFIX: fix KafkaStreams SmokeTest -- [...truncated 6686 lines...] kafka.network.SocketServerTest > tooBigRequestIsRejected STARTED kafka.network.SocketServerTest >

[jira] [Commented] (KAFKA-2700) delete topic should remove the corresponding ACL and configs

[ https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493958#comment-15493958 ] Parth Brahmbhatt commented on KAFKA-2700: - all yours. > delete topic should remove the

[GitHub] kafka pull request #1862: KAFKA-4175: Can't have StandbyTasks in KafkaStream...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1862 KAFKA-4175: Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1 standby tasks should be assigned per consumer not per process You can merge this pull request into a Git

[jira] [Commented] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

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

[jira] [Updated] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4175: -- Description: When we have StandbyTasks in a Kafka Streams app and we have > 1 threads per instance we

[jira] [Assigned] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4175: - Assignee: Damian Guy (was: Guozhang Wang) > Can't have StandbyTasks in KafkaStreams where

[jira] [Commented] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493763#comment-15493763 ] Guozhang Wang commented on KAFKA-4175: -- [~damianguy] Thanks for the finding. I think this was

[GitHub] kafka pull request #1861: HOTFIX: fix KafkaStreams SmokeTest

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1861 --- 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 #1858: HOTFIX: set sourceNodes to null for selectKey

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

[jira] [Commented] (KAFKA-3964) Metadata update requests are sometimes received after LeaderAndIsrRequests

[ https://issues.apache.org/jira/browse/KAFKA-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493523#comment-15493523 ] Jun Rao commented on KAFKA-3964: [~krishna97], it seems that this is the same issue as in

[GitHub] kafka pull request #1861: HOTFIX: fix KafkaStreams SmokeTest

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1861 HOTFIX: fix KafkaStreams SmokeTest Set the NUM_STREAM_THREADS_CONFIG = 1 in SmokeTestClient as we get locking issues when we have NUM_STREAM_THREADS_CONFIG > 1 and we have Standby Tasks, i.e.,

[jira] [Updated] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4175: -- Description: When we have StandbyTasks in a Kafka Streams app and we have > 1 threads per instance we

[jira] [Created] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

Damian Guy created KAFKA-4175: - Summary: Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1 Key: KAFKA-4175 URL: https://issues.apache.org/jira/browse/KAFKA-4175 Project: Kafka

[jira] [Updated] (KAFKA-4175) Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1

[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4175: -- Description: When we have {code}StandbyTasks{code} in a Kafka Streams app and we have > 1 threads per

[jira] [Updated] (KAFKA-4055) Add system tests for secure quotas

[ https://issues.apache.org/jira/browse/KAFKA-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4055: -- Status: Patch Available (was: Open) > Add system tests for secure quotas >

[jira] [Commented] (KAFKA-4055) Add system tests for secure quotas

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

[GitHub] kafka pull request #1860: KAFKA-4055: System tests for secure quotas

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1860 KAFKA-4055: System tests for secure quotas Fix existing client-id quota test which currently don't configure quota overrides correctly. Add new tests for user and (user, client-id) quota

Re: [VOTE] KIP-54: Sticky Partition Assignment Strategy

+1 (non-binding) On Wed, Sep 14, 2016 at 12:37 AM, Jason Gustafson wrote: > Thanks for the KIP. +1 from me. > > On Tue, Sep 13, 2016 at 12:05 PM, Vahid S Hashemian < > vahidhashem...@us.ibm.com> wrote: > > > Hi all, > > > > Thanks for providing feedback on this KIP so far. >

[jira] [Assigned] (KAFKA-4072) improving memory usage in LogCleaner

[ https://issues.apache.org/jira/browse/KAFKA-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4072: -- Assignee: Manikumar Reddy > improving memory usage in LogCleaner >

[jira] [Commented] (KAFKA-2700) delete topic should remove the corresponding ACL and configs

[ https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492770#comment-15492770 ] Manikumar Reddy commented on KAFKA-2700: [~parth.brahmbhatt]], are you working on this JIRA? If

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

See Changes: [wangguoz] KAFKA-4160: Ensure rebalance listener not called with coordinator lock -- [...truncated 5917 lines...] kafka.log.FileMessageSetTest > testPreallocateTrue STARTED

[jira] [Resolved] (KAFKA-4174) Delete a Config that does not exist in ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shunichi ishii resolved KAFKA-4174. --- Resolution: Not A Bug > Delete a Config that does not exist in ConsumerConfig >

[jira] [Commented] (KAFKA-4174) Delete a Config that does not exist in ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492652#comment-15492652 ] shunichi ishii commented on KAFKA-4174: --- sorry, it is not a bug. > Delete a Config that does not

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

See Changes: [wangguoz] KAFKA-4160: Ensure rebalance listener not called with coordinator lock -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

Re: [VOTE] 0.10.1 Release Plan

+1 (binding) On Tue, Sep 13, 2016 at 6:58 PM Becket Qin wrote: > +1 (non-binding) > > On Tue, Sep 13, 2016 at 5:33 PM, Dana Powers > wrote: > > > +1 > > > -- Thanks, Neha