[jira] [Created] (KAFKA-6380) transient failure in MetricsTest.testMetrics

Manikumar created KAFKA-6380: Summary: transient failure in MetricsTest.testMetrics Key: KAFKA-6380 URL: https://issues.apache.org/jira/browse/KAFKA-6380 Project: Kafka Issue Type: Bug

Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

+1 On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram wrote: > +1 > > Thanks, Ismael! > > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy wrote: > > > +1 > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma wrote: > > > > > Hi all, > > >

Re: [VOTE] KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

This vote has passed with 3 binding votes (Rajini, Jason, Guozhang) and one non-binding vote (Tom). Thanks you all for your participation. Thanks, Manikumar On Sat, Dec 2, 2017 at 4:07 AM, Guozhang Wang <wangg...@gmail.com> wrote: > Made a pass over the KIP. +1. > > Thanks!

Re: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

+1 (non-binding) On Thu, Nov 30, 2017 at 8:35 AM, Hu Xi wrote: > Hi all, > > As I didn't see any further discussion around this KIP, I'd like to start > voting. > > KIP documentation: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >

Re: [VOTE] KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

Bump up. waiting for few more binding votes. On Wed, Oct 18, 2017 at 6:57 PM, Rajini Sivaram <rajinisiva...@gmail.com> wrote: > +1 (binding) > > On Mon, Oct 9, 2017 at 5:32 PM, Manikumar <manikumar.re...@gmail.com> > wrote: > > > I'm bumping this up to get some

Re: Use self contained tokens instead of ACL

Hi, Yes, the token details and scram credentials are stored in Zookeeper and clients connects using tokenId and hmac for scram authentication. We plan to implement token storage as pluggable interface. Thanks, Manikumar On Thu, Nov 2, 2017 at 2:09 PM, Postmann, P. (Peter) < peter.po

Re: [VOTE] 1.0.0 RC4

+1 (non-binding). Verified quickstart, ran producer/consumer perf scripts, streams quickstart ran tests on src distribution. On Tue, Oct 31, 2017 at 8:42 PM, Ismael Juma wrote: > +1 (binding) from me. Tested the quickstart with the source and binary > (Scala 2.12) artifacts,

[jira] [Resolved] (KAFKA-2995) in 0.9.0.0 Old Consumer's commitOffsets with specify partition can submit not exists topic and partition to zk

[ https://issues.apache.org/jira/browse/KAFKA-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2995. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-2062) Sync Producer, Variable Message Length, Multiple Threads = Direct memory overuse

[ https://issues.apache.org/jira/browse/KAFKA-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2062. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1958) ZookeeperConsumerConnector doesn't remove consumer node on shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1958. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1415) Async producer.send can block forever if async.ProducerSendThread dies

[ https://issues.apache.org/jira/browse/KAFKA-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1415. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1066) Reduce logging on producer connection failures

[ https://issues.apache.org/jira/browse/KAFKA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1066. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported > Red

[jira] [Resolved] (KAFKA-1006) Consumer loses messages of a new topic with auto.offset.reset = largest

[ https://issues.apache.org/jira/browse/KAFKA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1006. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-610) connect.timeout.ms seems to do the wrong thing in the producer

[ https://issues.apache.org/jira/browse/KAFKA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-610. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported

[jira] [Resolved] (KAFKA-599) SimpleConsumerShell ONLY connects to the first host in the broker-list string to fetch topic metadata

[ https://issues.apache.org/jira/browse/KAFKA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-599. - Resolution: Auto Closed The Scala consumers are no longer supported. > SimpleConsumerShell O

[jira] [Resolved] (KAFKA-435) Keep track of the transient test failure for Kafka-343 on Apache Jenkins

[ https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-435. - Resolution: Cannot Reproduce Closing inactive issue. > Keep track of the transient test failure for Ka

[jira] [Resolved] (KAFKA-354) Refactor getter and setter API to conform to the new convention

[ https://issues.apache.org/jira/browse/KAFKA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-354. - Resolution: Won't Fix Closing inactive issue. > Refactor getter and setter API to conform to the

[jira] [Resolved] (KAFKA-407) Uncaught InputStream.close() exception in CompressionUtils.compress()

[ https://issues.apache.org/jira/browse/KAFKA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-407. - Resolution: Won't Fix This part of the code is removed. So closing the issue. > Uncau

[jira] [Resolved] (KAFKA-788) Periodic refresh of topic metadata on the producer doesn't include all topics

[ https://issues.apache.org/jira/browse/KAFKA-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-788. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. > Perio

Re: Use self contained tokens instead of ACL

lie...@opencore.com.invalid> wrote: > Hi Manikumar, > > I've looked over the KIP and had a quick look at the code in the PR as > well. In principle I think this would help Peter along depending on how > plugable some of the components are. Since Peter wants to generate Tokens > not in

[jira] [Resolved] (KAFKA-601) ConsumerConnector.shutdown() hangs if autocommit is enabled, and no zk available

[ https://issues.apache.org/jira/browse/KAFKA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-601. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported

[jira] [Resolved] (KAFKA-536) Kafka async appender/producer looses most messages

[ https://issues.apache.org/jira/browse/KAFKA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-536. - Resolution: Auto Closed Closing inactive issue. > Kafka async appender/producer looses most messa

[jira] [Resolved] (KAFKA-519) Allow commiting the state of single KafkaStream

[ https://issues.apache.org/jira/browse/KAFKA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-519. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > Al

[jira] [Resolved] (KAFKA-602) A ConsumerConnector that never receives messages does not shutdown cleanly

[ https://issues.apache.org/jira/browse/KAFKA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-602. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported

[jira] [Resolved] (KAFKA-623) It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector

[ https://issues.apache.org/jira/browse/KAFKA-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-623. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > It sho

[jira] [Resolved] (KAFKA-635) Producer error when trying to send not displayed unless in DEBUG logging level

[ https://issues.apache.org/jira/browse/KAFKA-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-635. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. > Producer er

[jira] [Resolved] (KAFKA-810) KafkaStream toString method blocks indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-810. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > KafkaStr

[jira] [Resolved] (KAFKA-845) Re-implement shallow iteration on 0.8.1

[ https://issues.apache.org/jira/browse/KAFKA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-845. - Resolution: Auto Closed Closing inactive issue. > Re-implement shallow iteration on 0.

[jira] [Resolved] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets

[ https://issues.apache.org/jira/browse/KAFKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-853. - Resolution: Won't Fix Closing inactive issue as per above comment. > Allow OffsetFetchRequ

[jira] [Resolved] (KAFKA-242) Subsequent calls of ConsumerConnector.createMessageStreams cause Consumer offset to be incorrect

[ https://issues.apache.org/jira/browse/KAFKA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-242. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > Subsequ

[jira] [Resolved] (KAFKA-243) Improve consumer connector documentation to include blocking semantics of kafka message streams

[ https://issues.apache.org/jira/browse/KAFKA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-243. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-250) Provide consumer iterator callback handler

[ https://issues.apache.org/jira/browse/KAFKA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-250. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported > Prov

[jira] [Resolved] (KAFKA-232) ConsumerConnector has no access to "getOffsetsBefore"

[ https://issues.apache.org/jira/browse/KAFKA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-232. - Resolution: Won't Fix Closing inactive issue. The old consumer is no longer supported. This jira

Re: [VOTE] KIP-214: Add zookeeper.max.in.flight.requests config to the broker

+1 (non-binding) On Fri, Oct 27, 2017 at 10:46 PM, Ted Yu wrote: > +1 > > On Fri, Oct 27, 2017 at 10:15 AM, Onur Karaman < > onurkaraman.apa...@gmail.com > > wrote: > > > I'd like to start the vote for KIP-214: Add > > zookeeper.max.in.flight.requests config to the broker >

[jira] [Resolved] (KAFKA-6019) Sentry permissions bug on CDH

[ https://issues.apache.org/jira/browse/KAFKA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6019. -- Resolution: Duplicate > Sentry permissions bug on

Re: Use self contained tokens instead of ACL

Hi, We have a accepted KIP for adding delegation token support for Kafka. https://cwiki.apache.org/confluence/display/KAFKA/KIP-48+Delegation+token+support+for+Kafka currently the PR is under review process. Maybe this can used be as starting point for your requirement.

Re: [VOTE] KIP-207:The Offsets which ListOffsetsResponse returns should monotonically increase even during a partition leader change

Thanks for the KIP. +1 (non-binding) On Thu, Oct 26, 2017 at 5:58 AM, Jason Gustafson wrote: > +1. Thanks for the KIP. > > On Mon, Oct 23, 2017 at 11:30 AM, Colin McCabe wrote: > > > On Mon, Oct 23, 2017, at 10:29, Jason Gustafson wrote: > > > Thanks

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

just a minor observation: Kafka binary contains two versions of javasist library (javassist-3.20.0-GA.jar, javassist-3.21.0-GA.jar). This dependency is coming from connect project. On Thu, Oct 19, 2017 at 2:16 AM, Guozhang Wang wrote: > Thanks for pointing out, Jun, Ismael.

Re: [VOTE] KIP-204 : adding records deletion operation to the new Admin Client API

+ (non-binding) Thanks, Manikumar On Tue, Oct 17, 2017 at 7:42 AM, Dong Lin <lindon...@gmail.com> wrote: > Thanks for the KIP. +1 (non-binding) > > On Wed, Oct 11, 2017 at 2:27 AM, Ted Yu <yuzhih...@gmail.com> wrote: > > > +1 > > > > On Mon, Oct 2

[jira] [Resolved] (KAFKA-4504) Details of retention.bytes property at Topic level are not clear on how they impact partition size

[ https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4504. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 1.0.0 > Details of retention.by

Re: [VOTE] KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

I'm bumping this up to get some attention :) On Wed, Sep 27, 2017 at 8:46 PM, Tom Bentley <t.j.bent...@gmail.com> wrote: > +1 (nonbinding) > > On 27 September 2017 at 16:10, Manikumar <manikumar.re...@gmail.com> > wrote: > > > Hi All, > > > > I

Re: [DISCUSS] KIP-186: Increase offsets retention default to 7 days

looks like VOTE thread is *NOT* started for this KIP. On Fri, Oct 6, 2017 at 11:23 PM, Manikumar <manikumar.re...@gmail.com> wrote: > looks like VOTE thread is started for this KIP. > > > On Wed, Aug 16, 2017 at 5:39 PM, Stevo Slavić <ssla...@gmail.com> wrote: >

Re: [DISCUSS] KIP-186: Increase offsets retention default to 7 days

looks like VOTE thread is started for this KIP. On Wed, Aug 16, 2017 at 5:39 PM, Stevo Slavić wrote: > +1 for making consistent default log and offsets retention time. > I like Stephane's suggestion too, log retention override should override > offset retention too if not

[jira] [Created] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

Manikumar created KAFKA-6005: Summary: Reject JoinGroup request from first member with empty protocol type/protocol list Key: KAFKA-6005 URL: https://issues.apache.org/jira/browse/KAFKA-6005 Project

[jira] [Resolved] (KAFKA-5369) Producer hangs on metadata fetch from broker in security authorization related failures and no meaningful exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5369. -- Resolution: Duplicate Resolving this as duplicate of KAFKA-4764, KAFKA-5920 > Producer ha

[VOTE] KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

Hi All, I'd like to start the vote on KIP-203. Details are here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-203%3A+Add+toLowerCase+support+to+sasl.kerberos.principal.to.local+rule Thanks,

Re: KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

Hi all, If there are no further concerns, I will start a VOTE thread for this minor KIP. Thanks On Tue, Sep 19, 2017 at 3:14 PM, Manikumar <manikumar.re...@gmail.com> wrote: > Thanks for the reviews. > > @Ted > Updated the KIP. > > @Tom > I think we can in

[jira] [Resolved] (KAFKA-5015) SASL/SCRAM authentication failures are hidden

[ https://issues.apache.org/jira/browse/KAFKA-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5015. -- Resolution: Duplicate Resolving as duplicate of KAFKA-4764 > SASL/SCRAM authentication failu

[jira] [Resolved] (KAFKA-5910) Kafka 0.11.0.1 Kafka consumer/producers retries in infinite loop when wrong SASL creds are passed

[ https://issues.apache.org/jira/browse/KAFKA-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5910. -- Resolution: Duplicate Resolving as duplicate of KAFKA-4764 > Kafka 0.11.0.1 Kafka consumer/produc

Re: KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

ent...@gmail.com> wrote: > What locale is used for the case conversion, the JVM default one or a > specific one? > > On 18 Sep 2017 5:31 pm, "Manikumar" <manikumar.re...@gmail.com> wrote: > > > Hi all, > > > > I've created a small KIP to extend the sasl

[jira] [Resolved] (KAFKA-5917) Kafka not starting

[ https://issues.apache.org/jira/browse/KAFKA-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5917. -- Resolution: Won't Fix These kinds of issues can be avoided once we completely move Kafka tools to Java

KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule

. Manikumar

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

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4454. -- Resolution: Fixed This is covered in KIP-189/KAFKA-5783 > Authorizer should also include the Princi

Re: MetricsReporter Does Not Receive Auto-generated Client Id

Hi, I think there is no specific reason. we can pass the clientId to MetricsReporter class's configure() method. Can you pls raise the JIRA? On Fri, Sep 15, 2017 at 7:44 AM, Kevin Lu wrote: > Hi, > > Is there a particular reason why the MetricsReporter class's

[jira] [Resolved] (KAFKA-3124) Update protocol wiki page to reflect latest request/response formats

[ https://issues.apache.org/jira/browse/KAFKA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3124. -- Resolution: Fixed KAFKA-3361 added support for generating protocol documentation page to Kafka docs

[jira] [Resolved] (KAFKA-1354) Failed to load class "org.slf4j.impl.StaticLoggerBinder"

[ https://issues.apache.org/jira/browse/KAFKA-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1354. -- Resolution: Fixed This was fixed in 0.8.2 by adding slf4j-log4j12 binding to Kafka libs. > Fai

[jira] [Resolved] (KAFKA-5177) Automatic creation of topic prompts warnings into console

[ https://issues.apache.org/jira/browse/KAFKA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5177. -- Resolution: Won't Fix As mentioned above, these are transient warning messages. Please reopen if you

[jira] [Resolved] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5296. -- Resolution: Fixed Closing as per above discussion. Multiple controllers can create these kind

[jira] [Resolved] (KAFKA-2887) TopicMetadataRequest creates topic if it does not exist

[ https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2887. -- Resolution: Fixed > TopicMetadataRequest creates topic if it does not ex

[jira] [Resolved] (KAFKA-1834) No Response when handle LeaderAndIsrRequest some case

[ https://issues.apache.org/jira/browse/KAFKA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1834. -- Resolution: Fixed This was fixed in newer Kafka versions. > No Response when han

[jira] [Resolved] (KAFKA-1630) ConsumerFetcherThread locked in Tomcat

[ https://issues.apache.org/jira/browse/KAFKA-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1630. -- Resolution: Cannot Reproduce Closing inactive issue. Please reopen if you think the issue still exists

Re: [VOTE] 0.11.0.1 RC0

+1 (non-binding) , verified artifacts, quick start using binary and ran tests on source artifact. Thanks for running the release. On Tue, Sep 12, 2017 at 4:30 PM, Ismael Juma wrote: > Hi Damian, > > Thanks for managing the release. This may just be the first ever RC0 to be >

[jira] [Resolved] (KAFKA-2392) Kafka Server does not accept 0 as a port

[ https://issues.apache.org/jira/browse/KAFKA-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2392. -- Resolution: Fixed Kafka supports port 0 for unit tests. As mentioned in the previous comment

[jira] [Resolved] (KAFKA-2319) After controlled shutdown: IllegalStateException: Kafka scheduler has not been started

[ https://issues.apache.org/jira/browse/KAFKA-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2319. -- Resolution: Fixed This was fixed in newer versions. Pl reopen if you think the issue still exists

[jira] [Resolved] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions

[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1817. -- Resolution: Fixed Fixed in KAFKA-1737 > AdminUtils.createTopic vs kafka-topics.sh --cre

[jira] [Resolved] (KAFKA-1608) Windows: Error: Could not find or load main class org.apache.zookeeper.server.quorum.QuorumPeerMain

[ https://issues.apache.org/jira/browse/KAFKA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1608. -- Resolution: Fixed This was fixed in newer versions. Pl reopen if you think the issue still exists

[jira] [Resolved] (KAFKA-251) The ConsumerStats MBean's PartOwnerStats attribute is a string

[ https://issues.apache.org/jira/browse/KAFKA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-251. - Resolution: Won't Fix Closing inactive issue as per above comments. > The ConsumerStats MBea

[jira] [Resolved] (KAFKA-5592) Connection with plain client to SSL-secured broker causes OOM

[ https://issues.apache.org/jira/browse/KAFKA-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5592. -- Resolution: Duplicate Marking this as duplicate of KAFKA-4493. > Connection with plain client to

[jira] [Resolved] (KAFKA-4638) Outdated and misleading link in section "End-to-end Batch Compression"

[ https://issues.apache.org/jira/browse/KAFKA-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4638. -- Resolution: Duplicate Resolving as duplicate of KAFKA-5686. PR Raised for KAFKA-5686 > Outda

[jira] [Resolved] (KAFKA-1037) switching to gzip compression no error message for missing snappy jar on classpath

[ https://issues.apache.org/jira/browse/KAFKA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1037. -- Resolution: Fixed This has been fixed in newer versions. > switching to gzip compression no er

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

[ https://issues.apache.org/jira/browse/KAFKA-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3033. -- Resolution: Duplicate Resolving this as a duplicate of KAFKA-4914. > Reassigning partition st

[jira] [Resolved] (KAFKA-4138) Producer data write network traffic to kafka brokers is increased for 50%

[ https://issues.apache.org/jira/browse/KAFKA-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4138. -- Resolution: Cannot Reproduce Closing inactive issue. Similar issues are fixed in newer versions. Pl

[jira] [Resolved] (KAFKA-4190) kafka-reassign-partitions does not report syntax problem in json

[ https://issues.apache.org/jira/browse/KAFKA-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4190. -- Resolution: Duplicate Resolving this duplicated KAFKA-4914. KAFKA-4914 PR is being reviewed now

[jira] [Resolved] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4119. -- Resolution: Cannot Reproduce Please reopen if the issue still exists. > Get topic offset with Ka

[jira] [Resolved] (KAFKA-4020) Kafka consumer stop taking messages from kafka server

[ https://issues.apache.org/jira/browse/KAFKA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4020. -- Resolution: Fixed Please reopen if the issue still exists. > Kafka consumer stop taking messa

[jira] [Resolved] (KAFKA-1993) Enable topic deletion as default

[ https://issues.apache.org/jira/browse/KAFKA-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1993. -- Resolution: Fixed Resolving this as duplicate of KAFKA-5384 > Enable topic deletion as defa

[jira] [Resolved] (KAFKA-3113) Kafka simple consumer inconsistent result

[ https://issues.apache.org/jira/browse/KAFKA-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3113. -- Resolution: Cannot Reproduce may be seed broker is different for different topics. simpleconsumer

[jira] [Resolved] (KAFKA-2022) simpleconsumer.fetch(req) throws a java.nio.channels.ClosedChannelException: null exception when the original leader fails instead of being trapped in the fetchResponse

[ https://issues.apache.org/jira/browse/KAFKA-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2022. -- Resolution: Won't Fix I think we need to catch the exception and retry with a new leader. Pl reopen

[jira] [Resolved] (KAFKA-2595) Processor thread dies due to an uncaught NoSuchElementException

[ https://issues.apache.org/jira/browse/KAFKA-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2595. -- Resolution: Fixed See the discussion in KAFKA-1804 > Processor thread dies due to an uncau

[jira] [Resolved] (KAFKA-2623) Kakfa broker not deleting logs after configured retention time properly

[ https://issues.apache.org/jira/browse/KAFKA-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2623. -- Resolution: Fixed Time-based log retention is enforced in KIP-33. Pl reopen if you think the issue

[jira] [Resolved] (KAFKA-2166) Recreation breaks topic-list

[ https://issues.apache.org/jira/browse/KAFKA-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2166. -- Resolution: Fixed Deletion related issues are fixed in newer versions. Pl reopen if you think

[jira] [Resolved] (KAFKA-1563) High packet rate between brokers in kafka cluster.

[ https://issues.apache.org/jira/browse/KAFKA-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1563. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > High packet r

[jira] [Resolved] (KAFKA-1455) Expose ConsumerOffsetChecker as an api instead of being command line only

[ https://issues.apache.org/jira/browse/KAFKA-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1455. -- Resolution: Fixed This is has been added to Java Admin API. > Expose ConsumerOffsetChecker as an

[jira] [Resolved] (KAFKA-47) Create topic support and new ZK data structures for intra-cluster replication

[ https://issues.apache.org/jira/browse/KAFKA-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-47. Resolution: Fixed Closing this umbrella JIRA as all tasks are resolved. > Create topic support and new

[jira] [Resolved] (KAFKA-641) ConsumerOffsetChecker breaks when using dns names x.b.com as opposed to raw public IP for broker.

[ https://issues.apache.org/jira/browse/KAFKA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-641. - Resolution: Fixed This is not relevant in newer versions. > ConsumerOffsetChecker breaks when using

[jira] [Resolved] (KAFKA-252) Generalize getOffsetsBefore API to a new more general API getLeaderMetadata

[ https://issues.apache.org/jira/browse/KAFKA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-252. - Resolution: Fixed These API were handled in newer versions. > Generalize getOffsetsBefore API to a

[jira] [Resolved] (KAFKA-980) Crash during log recovery can cause full recovery to never run

[ https://issues.apache.org/jira/browse/KAFKA-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-980. - Resolution: Fixed > Crash during log recovery can cause full recovery to never

[jira] [Resolved] (KAFKA-986) Topic Consumption Across multiple instances of consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-986. - Resolution: Cannot Reproduce > Topic Consumption Across multiple instances of consumer gro

[jira] [Resolved] (KAFKA-1093) Log.getOffsetsBefore(t, …) does not return the last confirmed offset before t

[ https://issues.apache.org/jira/browse/KAFKA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1093. -- Resolution: Invalid relavent part of the code is not available now. So closing this now

[jira] [Resolved] (KAFKA-1197) Count of bytes or messages of a topic stored in kafka

[ https://issues.apache.org/jira/browse/KAFKA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1197. -- Resolution: Fixed Size, LogStartOffset, LogEndOffset are exposed as metrics in newer verions. > Co

[jira] [Resolved] (KAFKA-805) log.append() may fail with a compressed messageset containing no uncompressed messages

[ https://issues.apache.org/jira/browse/KAFKA-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-805. - Resolution: Fixed Not able to reproduce the issue. looks like this got fixed in newer versions

Re: [VOTE] KIP-188 - Add new metrics to support health checks

+1 (non-binding) On Mon, Sep 4, 2017 at 6:39 PM, Rajini Sivaram wrote: > All the suggestions on the discuss thread have been incorporated into the > KIP. Please let me know if you have any more concerns or else can we > proceed with voting for this KIP? > > Thank you, >

[jira] [Resolved] (KAFKA-1946) Fix various broker metrics

[ https://issues.apache.org/jira/browse/KAFKA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1946. -- Resolution: Fixed > Fix various broker metrics > -- > >

[jira] [Resolved] (KAFKA-1962) Restore delayed request metrics

[ https://issues.apache.org/jira/browse/KAFKA-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1962. -- Resolution: Fixed > Restore delayed request metr

[jira] [Resolved] (KAFKA-1505) Broker failed to start because of corrupted replication-offset-checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1505. -- Resolution: Fixed This was fixed in newer versions. Pl reopen if you think the issue still exists

[jira] [Resolved] (KAFKA-3059) ConsumerGroupCommand should allow resetting offsets for consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3059. -- Resolution: Duplicate This functionality is implemented in KAFKA-4743 > ConsumerGroupCommand sho

[jira] [Resolved] (KAFKA-4264) kafka-server-stop.sh fails is Kafka launched via kafka-server-start.sh

[ https://issues.apache.org/jira/browse/KAFKA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4264. -- Resolution: Duplicate This is related to KAFKA-4931. PR is available for KAFKA-4931. > kafka-ser

[jira] [Resolved] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4337. -- Resolution: Won't Fix > Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic J

[jira] [Resolved] (KAFKA-4411) broker don't have access to kafka zookeeper nodes

[ https://issues.apache.org/jira/browse/KAFKA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4411. -- Resolution: Not A Problem It is necessary to have the same principal name across all brokers for ZK

[jira] [Resolved] (KAFKA-4188) compilation issues with org.apache.kafka.clients.consumer.internals.Fetcher.java

[ https://issues.apache.org/jira/browse/KAFKA-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4188. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > compilation iss

<    3   4   5   6   7   8   9   10   11   12   >