Re: [VOTE] KIP-175: Additional '--describe' views for ConsumerGroupCommand

+1 (non-binding) On Fri, Aug 11, 2017 at 8:09 PM, Mickael Maison wrote: > +1 non-binding, thanks Vahid > > On Wed, Aug 9, 2017 at 9:31 PM, Jason Gustafson > wrote: > > Thanks for the KIP. +1 > > > > On Thu, Jul 27, 2017 at 2:04 PM, Vahid S

Re: [VOTE] KIP-163: Lower the Minimum Required ACL Permission of OffsetFetch

+1 (non-binding) On Fri, Aug 11, 2017 at 5:31 AM, Jun Rao wrote: > Hi, Vahid, > > Thanks for the KIP. +1 from me. > > Jun > > On Wed, Aug 2, 2017 at 2:40 PM, Vahid S Hashemian < > vahidhashem...@us.ibm.com > > wrote: > > > Hi all, > > > > Thanks to everyone who participated

[jira] [Resolved] (KAFKA-3389) ReplicaStateMachine areAllReplicasForTopicDeleted check not handling well case when there are no replicas for topic

[ https://issues.apache.org/jira/browse/KAFKA-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3389. -- Resolution: Won't Fix As mentioned in the previous comment, this may not be an issue. Pl reopen

Re: Usage of SSL_ENDPOINT_IDENTIFICATION_ALGORITHM_CONFIG

check here: https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/security/ssl/SslFactory.java#L84 On Thu, Aug 10, 2017 at 3:49 AM, M. Manna wrote: > Hello, > > I have been trying to find the usage of this property within Kafka source. >

[jira] [Created] (KAFKA-5644) Transient test failure: ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime

Manikumar created KAFKA-5644: Summary: Transient test failure: ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime Key: KAFKA-5644 URL: https://issues.apache.org/jira/browse/KAFKA-5644 Project

[jira] [Commented] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

[ https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015313#comment-16015313 ] Manikumar commented on KAFKA-2651: -- [~ijuma] We have deprecated the alter config in 0.9.0. current docs

Re: [VOTE] 0.10.2.1 RC1

+1 (non-binding) Verified artifacts and quick start On Mon, Apr 17, 2017 at 8:05 PM, Mathieu Fenniak < mathieu.fenn...@replicon.com> wrote: > +1 (non-binding) > > Upgraded KS & KC applications to 0.10.2.1 RC1, successfully ran > application-level acceptance tests. > > Mathieu > > > On Wed, Apr

[jira] [Resolved] (KAFKA-1516) Producer Performance Test sends messages with bytes of 0x0

[ https://issues.apache.org/jira/browse/KAFKA-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1516. -- Resolution: Fixed Resolving this as support for passing custom message payloads is given in KAFKA

Re: Doubts regarding KafkaProducer implemetation

Hi, java producer waits for the metadata of the given topic to be available. We will get TimeoutException if we didn't get metadata within max.block.ms. As observed by you, this behavior is different from old producer. "retries" config is not applicable to metadata fetch. We can adjust

[jira] [Resolved] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3990. -- Resolution: Duplicate > Kafka New Producer may raise an OutOfMemoryEr

[jira] [Resolved] (KAFKA-3391) Kafka to ZK timeout

[ https://issues.apache.org/jira/browse/KAFKA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3391. -- Resolution: Not A Problem Please reopen if the issue still exists. > Kafka to ZK time

[jira] [Resolved] (KAFKA-1436) Idempotent Producer / Duplicate Detection

[ https://issues.apache.org/jira/browse/KAFKA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1436. -- Resolution: Duplicate > Idempotent Producer / Duplicate Detect

[jira] [Resolved] (KAFKA-639) RESTful proxy

[ https://issues.apache.org/jira/browse/KAFKA-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-639. - Resolution: Duplicate > RESTful proxy > - > > Ke

[jira] [Resolved] (KAFKA-4807) Kafka broker fail over bug in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4807. -- Resolution: Duplicate > Kafka broker fail over bug in zookee

[jira] [Closed] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

[ https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar closed KAFKA-4864. > Kafka Secure Migrator tool doesn't secure all the no

[jira] [Comment Edited] (KAFKA-4795) Confusion around topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894178#comment-15894178 ] Manikumar edited comment on KAFKA-4795 at 3/3/17 11:26 AM: --- [~vahid] If we

[jira] [Commented] (KAFKA-4795) Confusion around topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894178#comment-15894178 ] Manikumar commented on KAFKA-4795: -- [~vahid] If we disable topic deletion then we clearing the delete

[jira] [Commented] (KAFKA-4807) Kafka broker fail over bug in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894097#comment-15894097 ] Manikumar commented on KAFKA-4807: -- This is related to KAFKA-3959. offsets.topic.replication.factor

[jira] [Comment Edited] (KAFKA-4788) Broker level configuration 'log.segment.bytes' not used when 'segment.bytes' not configured per topic.

[ https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880385#comment-15880385 ] Manikumar edited comment on KAFKA-4788 at 2/23/17 1:03 PM: --- [~ijuma] While

[jira] [Commented] (KAFKA-4788) Broker level configuration 'log.segment.bytes' not used when 'segment.bytes' not configured per topic.

[ https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880385#comment-15880385 ] Manikumar commented on KAFKA-4788: -- [~ijuma] While using kafka-topics.sh, we are doing topic-level

[jira] [Commented] (KAFKA-4788) Broker level configuration 'log.segment.bytes' not used when 'segment.bytes' not configured per topic.

[ https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880281#comment-15880281 ] Manikumar commented on KAFKA-4788: -- looks like KAFKA-4092 change introduced this issue. During

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

; > > > > > gharatmayures...@gmail.com > > > > > > wrote: > > > > > > > > > > > Hi Jun, > > > > > > > > > > > > Sure sounds good to me. > > > > > > > > > > > > Th

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

kafka-acls.sh would > > work with this change, on the ticket, we designed a detailed solution to > > make this tool generally usable with all sorts of combinations of > > Authorizers and PrincipalBuilders and give more flexibility to the end > > users. > > Without the

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Sorry, I am late to this discussion. PrincipalBuilder is only used for SSL Protocol. For SASL, we use "sasl.kerberos.principal.to.local.rules" config to map SASL principal names to short names. To make it consistent, Do we also need to pass the SASL full principal name to authorizer ? We may need

[jira] [Assigned] (KAFKA-4542) Add authentication based on delegation token.

[ https://issues.apache.org/jira/browse/KAFKA-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4542: -- Assignee: Manikumar Reddy > Add authentication based on delegation to

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

Thank you all for your votes and feedback. The vote has passed with 4 binding votes(Gwen, Jun, Grant, Harsha) and 2 non-binding votes(Roger, Dong Lin). I have updated the relevant wiki pages. Thanks Manikumar On Tue, Feb 14, 2017 at 12:02 AM, Dong Lin <lindon...@gmail.com> wrote: >

[jira] [Resolved] (KAFKA-3531) support subnet in ACL tool

[ https://issues.apache.org/jira/browse/KAFKA-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3531. Resolution: Duplicate Assignee: (was: Parth Brahmbhatt) Resolving

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

Yes, owners and the renewers can always describe their own tokens. Updated the KIP. On Sat, Feb 11, 2017 at 3:12 AM, Jun Rao wrote: > Hi, Mani, > > Thanks for the update. Just a minor comment below. Otherwise, +1 from me. > > > > > > > > > > 116. Could you document the ACL

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

end the support to allow a user to acquire delegation tokens for other users, then we can enable CREATE/DELETE operations. Updated the KIP. Thanks, Manikumar > On Wed, Feb 8, 2017 at 1:35 AM, Manikumar <manikumar.re...@gmail.com> > wrote: > > > Hi Jun, > > > > &g

[jira] [Resolved] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-4076. Resolution: Invalid Pl reopen the issue, if still exists. > Kafka broker shuts down

[jira] [Commented] (KAFKA-4751) kafka-clients-0.9.0.2.4.2.11-1 issue not throwing exception.

[ https://issues.apache.org/jira/browse/KAFKA-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859568#comment-15859568 ] Manikumar Reddy commented on KAFKA-4751: It is a known issue. Related JIRA is KAFKA-1894

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

> > > > > > It would also be helpful for others to give feedback on this KIP. > Rajini, > > > Gwen, Ismael? > > > > > > Thanks, > > > > > > Jun > > > > > > > > > On Sun, Feb 5, 2017 at 9:54 AM, Manikumar <m

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

thread for impersonation related discussion. Thanks, Manikumar On Wed, Feb 8, 2017 at 8:37 AM, Roger Hoover <roger.hoo...@gmail.com> wrote: > Hi Jun, > > How does it allow impersonation at the connection level? Looking at the > KIP, the DelegationTokenRequest does not have an &quo

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

Agree, we can run the token expiry check thread as part of controller broker. WIll update the KIP. Thanks, Manikumar > > On Sun, Feb 5, 2017 at 9:54 AM, Manikumar <manikumar.re...@gmail.com> > wrote: > > > Hi Jun, > > > > Please see the replies inline. >

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

+1 for ismael's suggestion. grouping of methods by the relevant resource will simply the API. In future, we will be adding delegation token related operations to admin client. I can imagine methods like adminClient.token().create(...), adminClient.token().renew(...), etc.. Thanks, Manikumar

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

n authentication time. > > > 110. The diagrams in the wiki still show MD5 digest. Could you change it to > SCRAM? > > Updated the diagram. Thanks, Manikumar > > > > > > Thanks. > > Manikumar > > > > > > > > > > On Fri, De

[jira] [Commented] (KAFKA-4541) Add capability to create delegation token

[ https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837319#comment-15837319 ] Manikumar Reddy commented on KAFKA-4541: [~singhashish] Can you post your WIP PR? So that I can

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

terminology tokenUID => tokenID. > 107.3 How does each broker know about changes in tokens? Does each broker > register a watcher for /tokenauth/tokens? > Yes, the changes are updated through zk notifications. > 107.4 How is token deletion handled? Does every broker delete the same

[VOTE] KIP-48 Support for delegation tokens as an authentication mechanism

Hi, I would like to initiate the vote on KIP-48: https://cwiki.apache.org/confluence/display/KAFKA/KIP-48+ Delegation+token+support+for+Kafka Thanks, Manikumar

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

Hi Devs, If there are no more comments, I will start vote on this KIP later this week. Thanks On Fri, Dec 16, 2016 at 12:28 PM, Manikumar <manikumar.re...@gmail.com> wrote: > Hi, > > >> Can you add a sample Jaas configuration using delegation tokens to the >> KIP?

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

give any suggestions/concerns on this KIP. Thanks, > > On Thu, Dec 15, 2016 at 9:04 AM, Manikumar <manikumar.re...@gmail.com> > wrote: > > > @Gwen, @Rajini, > > > > As mentioned in the KIP, main motivation for this KIP is to reduce load > on > > Kerberos >

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751936#comment-15751936 ] Manikumar Reddy commented on KAFKA-1696: Thanks for creating sub-tasks. About authentication, we

[jira] [Commented] (KAFKA-4541) Add capability to create delegation token

[ https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751744#comment-15751744 ] Manikumar Reddy commented on KAFKA-4541: [~singhashish] Is this JIRA work includes token storage

[jira] [Assigned] (KAFKA-4543) Add capability to renew/expire delegation tokens.

[ https://issues.apache.org/jira/browse/KAFKA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4543: -- Assignee: Manikumar Reddy > Add capability to renew/expire delegation tok

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

for authentication and tokenID for retrial of tokenHmac at server side. Does above sound OK? Thanks, Manikumar On Wed, Dec 14, 2016 at 10:33 PM, Harsha Chintalapani <ka...@harsha.io> wrote: > @Gwen @Mani Not sure why we want to authenticate at every request. Even if > the to

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

? > Kafka Connect, NiFi and friends can probably use this to share clients > between multiple jobs, tasks, etc. > > What do you think? > > Gwen > > On Tue, Dec 13, 2016 at 12:43 AM, Manikumar <manikumar.re...@gmail.com> > wrote: > > > Ashish, > > >

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15747403#comment-15747403 ] Manikumar Reddy commented on KAFKA-1696: [~singhashish] Yes, Pl go ahead and create sub-jiras

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

en for a specified amount of time? In > current version of KIP, renew request does not take time as a param, not > sure what is expiry time set to after renewal. > > Yes, we need to specify renew period. I'll update the KIP. Thanks, Mankumar > > On Mon, Dec 12, 2016 at 9:08 AM

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742486#comment-15742486 ] Manikumar Reddy commented on KAFKA-1696: .[~singhashish] Sorry for the late reply. I reinitiated

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

+Delegation+token+support+for+Kafka Jun, Ashish, Gwen, Pl review the updated KIP. Thanks Manikumar On Thu, Sep 29, 2016 at 9:56 PM, Ashish Singh <asi...@cloudera.com> wrote: > Harsha/ Gwen, > > How do we proceed here? I am willing to help out with here. > > On Fri, Sep 23, 2

Re: Reg: ACLS

The default principal for Plaintext transport is "ANONYMOUS". On Sun, Dec 11, 2016 at 12:58 AM, BigData dev wrote: > Hi, > > bin/kafka-acls.sh --topic kafka-testtopic --add -allow-host 9.30.15.19 > --operation Write --authorizer-properties >

Re: [DISCUSS] KIP-80: Kafka REST Server

for raising valid queries and helping me to improve the KIP details. I will discuss some of your notes (new consumer API, HTTP/2, multi-REST-proxy etc) at kafka-rest project issues page . Thanks you all for participating in this discussion. Thanks, Manikumar On Wed, Oct 26, 2016 at 11:56 AM

Re: [ANNOUNCE] Apache Kafka 0.10.1.0 Released

> > > > > > > > and binary releases from > > > > > > https://www.apache.org/dyn/closer.cgi?path=/kafka/0.10.1.0/k > > > > > > afka_2.11-0.10.1.0.tgz > > > > > > https://www.apache.org/dyn/closer.cgi?path=/kafka/0.10.1.0/k

Re: [kafka-clients] [VOTE] 0.10.1.0 RC3

+1 (non-binding) verified quick start and artifacts. On Sat, Oct 15, 2016 at 4:59 AM, Jason Gustafson wrote: > Hello Kafka users, developers and client-developers, > > One more RC for 0.10.1.0. We're hoping this is the final one so that we > can meet the release target date

Re: [DISCUSS] KIP-80: Kafka REST Server

ess number of distributions/builds. Thanks, Manikumar On Sat, Oct 1, 2016 at 4:24 AM, Jay Kreps <j...@confluent.io> wrote: > Hey guys, > > There's already a REST interface maintained as a separate project--it's > open source and apache licensed and actively maintained ( > https://git

[jira] [Commented] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528682#comment-15528682 ] Manikumar Reddy commented on KAFKA-4074: [~hachikuji] Yes, resolving this as duplicate

[jira] [Resolved] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-4074. Resolution: Duplicate > Deleting a topic can make it unavailable e

[DISCUSS] KIP-80: Kafka REST Server

://cwiki.apache.org/confluence/display/KAFKA/KIP- 80%3A+Kafka+Rest+Server Your comments and feedback are welcome. Thanks, Manikumar

[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] [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

[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 rem

[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 LogClea

[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

[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=15490118#comment-15490118 ] Manikumar Reddy commented on KAFKA-4126: [~vahid] I think, I tried by disabling auto.topic.create

Re: Not able to download tests jar of kafka and kafka-streams from maven repo.

adding missing classifier parameter.. org.apache.kafka kafka-streams 0.10.0.0 test-jar test On Tue, Sep 13, 2016 at 12:07 PM, Manikumar Reddy <manikumar.re...@gmail.com > wrote: > Hi, > > Kafka uses "test" as classifier (default is "tests" ) for test

Re: Not able to download tests jar of kafka and kafka-streams from maven repo.

Hi, Kafka uses "test" as classifier (default is "tests" ) for test jars. We can add test parameter to dependency tag to resolve the error. org.apache.kafka kafka-streams 0.10.0.0 test-jar test Thanks Ma

[jira] [Commented] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469613#comment-15469613 ] Manikumar Reddy commented on KAFKA-4074: [~junrao] Yes, Both issues are same. I can merge my

[jira] [Commented] (KAFKA-4111) broker compress data of certain size instead on a produce request

[ https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469580#comment-15469580 ] Manikumar Reddy commented on KAFKA-4111: Ok got it. Broker handles each producer request

[jira] [Commented] (KAFKA-4111) broker compress data of certain size instead on a produce request

[ https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466584#comment-15466584 ] Manikumar Reddy commented on KAFKA-4111: "compression.type" broker config property is

[jira] [Commented] (KAFKA-4109) kafka client send msg exception

[ https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466570#comment-15466570 ] Manikumar Reddy commented on KAFKA-4109: Enable producer debug logs to get root cause

[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=15466496#comment-15466496 ] Manikumar Reddy commented on KAFKA-4126: Currently producer logs below warn message. May be we

Re: WARN log message flooding broker logs for a pretty typical SSL setup

We don't need JIRA for minor PRs. Just prefix "MINOR:" to PR title. On Tue, Sep 6, 2016 at 9:16 AM, Jaikiran Pai wrote: > Thanks Ismael, I'll raise a PR for this. As a process, is there a JIRA > that's expected to be filed for this before I raise a PR or would this be

[jira] [Commented] (KAFKA-4065) Property missing in ProcuderConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436585#comment-15436585 ] Manikumar Reddy commented on KAFKA-4065: Agree, currently new producer don't support

[jira] [Assigned] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4074: -- Assignee: Manikumar Reddy > Deleting a topic can make it unavailable e

[jira] [Commented] (KAFKA-4065) Property missing in ProcuderConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434215#comment-15434215 ] Manikumar Reddy commented on KAFKA-4065: "compression.type" config property is u

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432667#comment-15432667 ] Manikumar Reddy commented on KAFKA-3218: [~ rajinisivaram]KAFKA-3680 fixes this issue right

[jira] [Commented] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432252#comment-15432252 ] Manikumar Reddy commented on KAFKA-4076: You are storing kafka data logs to /tmp folder

[jira] [Resolved] (KAFKA-3204) ConsumerConnector blocked on Authenticated by SASL Failed.

[ https://issues.apache.org/jira/browse/KAFKA-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3204. Resolution: Won't Fix > ConsumerConnector blocked on Authenticated by SASL Fai

Re: [VOTE] KIP-74: Add FetchResponse size limit in bytes

+1 (non-binding) This feature help us control memory footprint and allows consumer to progress on fetching large messages. On Fri, Aug 19, 2016 at 10:32 AM, Gwen Shapira wrote: > +1 (binding) > > On Thu, Aug 18, 2016 at 1:47 PM, Andrey L. Neporada >

[jira] [Resolved] (KAFKA-4063) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-4063. Resolution: Duplicate > Add support for infinite endpoints for range queries in Ka

[jira] [Resolved] (KAFKA-2199) Make signing artifacts optional, setting maven repository possible from command line

[ https://issues.apache.org/jira/browse/KAFKA-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-2199. Resolution: Fixed > Make signing artifacts optional, setting maven repository possible f

Re: Do not log value of configs that Kafka doesn't recognize

During server/client startup, we are logging all the supplied configs. May be we can just mask the password related config values for both valid/invalid configs. On Wed, Aug 17, 2016 at 5:14 PM, Jaikiran Pai wrote: > Any opinion about this proposed change? > >

[jira] [Comment Edited] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424315#comment-15424315 ] Manikumar Reddy edited comment on KAFKA-3980 at 8/17/16 11:22 AM

[jira] [Commented] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424315#comment-15424315 ] Manikumar Reddy commented on KAFKA-3980: as suspected, this may be related to quota leak : KAFKA

[jira] [Updated] (KAFKA-4035) AclCommand should allow Describe operation on groups

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

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419140#comment-15419140 ] Manikumar Reddy commented on KAFKA-3959: Yes, min.insync.replicas applicable to internal topics

[jira] [Updated] (KAFKA-4012) KerberosShortNamer should implement toString()

[ https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4012: --- Status: Patch Available (was: Open) > KerberosShortNamer should implement toStr

[jira] [Updated] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4035: --- Affects Version/s: 0.9.0.0 0.10.0.0 0.10.0.1

[jira] [Updated] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4035: --- Status: Patch Available (was: Open) > AclCommand should allow Describe operation on gro

[jira] [Assigned] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4035: -- Assignee: Manikumar Reddy > AclCommand should allow Describe operation on gro

[jira] [Comment Edited] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418751#comment-15418751 ] Manikumar Reddy edited comment on KAFKA-3959 at 8/12/16 1:27 PM: - looks

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418751#comment-15418751 ] Manikumar Reddy commented on KAFKA-3959: looks like this is done on purpose. While creating

[jira] [Resolved] (KAFKA-1612) Consumer offsets auto-commit before processing finishes

[ https://issues.apache.org/jira/browse/KAFKA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-1612. Resolution: Won't Fix Closing this issue in favor new consumer API. > Consumer offs

Re: [VOTE] KIP-70: Revise Partition Assignment Semantics on New Consumer's Subscription Change

+1 (non-binding) On Wed, Aug 10, 2016 at 8:30 AM, Ewen Cheslack-Postava wrote: > +1 (binding), thanks for working on this Vahid. > > @Dana - See https://cwiki.apache.org/confluence/display/KAFKA/Bylaws re: > binding/non-binding, although I now notice that we specify criteria

Re: [kafka-clients] [VOTE] 0.10.0.1 RC2

t; details: >> >> http://home.apache.org/~ijuma/kafka-0.10.0.1-rc2/RELEASE_NOTES.html >> >> When compared to RC1, RC2 contains a fix for a regression where an older >> version of slf4j-log4j12 was also being included in the libs folder of the >> binary tarball (KAFKA

Re: [kafka-clients] [VOTE] 0.10.0.1 RC1

Hi, There are two versions of slf4j-log4j jar in the build. (1.6.1, 1.7.21). slf4j-log4j12-1.6.1.jar is coming from streams:examples module. Thanks, Manikumar On Tue, Aug 2, 2016 at 8:31 PM, Ismael Juma <ism...@juma.me.uk> wrote: > Hello Kafka users, developers and client-d

[jira] [Updated] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3950: --- Affects Version/s: (was: 0.10.0.0) 0.9.0.0 > kafka mirror ma

[jira] [Updated] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3950: --- Reviewer: Ismael Juma Fix Version/s: 0.10.0.1 > kafka mirror maker t

<    5   6   7   8   9   10   11   12   13   14   >