[jira] [Resolved] (KAFKA-2451) Exception logged but not managed

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

[jira] [Resolved] (KAFKA-2414) Running kafka-producer-perf-test.sh with " --messages 10000000 --message-size 1000 --new-producer" will get WARN Error in I/O.

[ https://issues.apache.org/jira/browse/KAFKA-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2414. -- Resolution: Cannot Reproduce This might have been fixed in latest versions. Pl reopen if you think the

[jira] [Resolved] (KAFKA-3885) Kafka new producer cannot failover

[ https://issues.apache.org/jira/browse/KAFKA-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3885. -- Resolution: Duplicate > Kafka new producer cannot failo

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

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

[jira] [Resolved] (KAFKA-4350) Can't mirror from Kafka 0.9 to Kafka 0.10.1

[ https://issues.apache.org/jira/browse/KAFKA-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4350. -- Resolution: Won't Fix Closing as per comments. > Can't mirror from Kafka 0.9 to

[jira] [Resolved] (KAFKA-4869) 0.10.2.0 release notes incorrectly include KIP-115

[ https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4869. -- Resolution: Fixed Assignee: Manikumar > 0.10.2.0 release notes incorrectly include KIP-

[jira] [Resolved] (KAFKA-4634) Issue of one kafka brokers not listed in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4634. -- Resolution: Fixed Similar issue fixed in KAFKA-1387/Newer versions. Pl reopen if you think the issue

[jira] [Resolved] (KAFKA-1636) High CPU in very active environment

[ https://issues.apache.org/jira/browse/KAFKA-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1636. -- Resolution: Won't Fix ConsumerIterator waits for the data from the underlying stream. Pl reopen if

[jira] [Resolved] (KAFKA-2173) Kafka died after throw more error

[ https://issues.apache.org/jira/browse/KAFKA-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2173. -- Resolution: Cannot Reproduce Might have fixed in latest versions. Pl reopen if you think the issue

[jira] [Resolved] (KAFKA-1675) bootstrapping tidy-up

[ https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1675. -- Resolution: Fixed gradlew, gradlew.bat scripts are removed from repo. Pl reopen if you think the

[jira] [Resolved] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1980. -- Resolution: Fixed Closing as per comments. Pl reopen if you think the issue still exists > Cons

[jira] [Resolved] (KAFKA-3570) It'd be nice to line up display output in columns in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3570. -- Resolution: Fixed > It'd be nice to line up display output in columns in ConsumerGrou

[jira] [Resolved] (KAFKA-4297) Cannot Stop Kafka with Shell Script

[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4297. -- Resolution: Duplicate Closing this as there is a latest PR for KAFKA-4931. > Cannot Stop Kafka w

[jira] [Resolved] (KAFKA-4389) kafka-server.stop.sh not work

[ https://issues.apache.org/jira/browse/KAFKA-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4389. -- Resolution: Duplicate > kafka-server.stop.sh not w

[jira] [Reopened] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reopened KAFKA-1980: -- > Console consumer throws OutOfMemoryError with large max-messa

[jira] [Resolved] (KAFKA-1980) Console consumer throws OutOfMemoryError with large max-messages

[ https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1980. -- Resolution: Won't Fix [~ndimiduk] Agree. Updated the JIRA. > Console consumer throws OutOfMem

[jira] [Resolved] (KAFKA-888) problems when shutting down the java consumer .

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

[jira] [Resolved] (KAFKA-1463) producer fails with scala.tuple error

[ https://issues.apache.org/jira/browse/KAFKA-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1463. -- Resolution: Won't Fix Pl reopen if you think the issue still exists > producer fa

[jira] [Resolved] (KAFKA-1632) No such method error on KafkaStream.head

[ https://issues.apache.org/jira/browse/KAFKA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1632. -- Resolution: Cannot Reproduce Mostly related to Kafka version mismatch. Pl reopen if you think the

[jira] [Resolved] (KAFKA-1492) Getting error when sending producer request at the broker end with a single broker

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

[jira] [Resolved] (KAFKA-270) sync producer / consumer test producing lot of kafka server exceptions & not getting the throughput mentioned here http://incubator.apache.org/kafka/performance.html

[ https://issues.apache.org/jira/browse/KAFKA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-270. - Resolution: Won't Fix Closing due to inactivity. Pl reopen if you think the issue still exists &g

[jira] [Resolved] (KAFKA-4520) Kafka broker fails with not so user-friendly error msg when log.dirs is not set

[ https://issues.apache.org/jira/browse/KAFKA-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4520. -- Resolution: Fixed Fix Version/s: 0.11.0.0 > Kafka broker fails with not so user-friendly er

[jira] [Resolved] (KAFKA-1347) Create a system test for network partitions

[ https://issues.apache.org/jira/browse/KAFKA-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1347. -- Resolution: Duplicate This is being fixed in KAFKA-5476. > Create a system test for network partiti

[jira] [Resolved] (KAFKA-818) Request failure metrics on the Kafka brokers is not instrumented for all requests

[ https://issues.apache.org/jira/browse/KAFKA-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-818. - Resolution: Duplicate Similar metrics are proposed in KAFKA-5746. > Request failure metrics on the Ka

[jira] [Resolved] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

[ https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1447. -- Resolution: Fixed Pl reopen if you think the issue still exists > Controlled shutdown deadlock w

[jira] [Resolved] (KAFKA-1402) Create unit test helper that stops and starts a cluster

[ https://issues.apache.org/jira/browse/KAFKA-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1402. -- Resolution: Fixed We have KafkaServerTestHarness, EmbeddedKafkaCluster, EmbeddedZookeeper helper

[jira] [Resolved] (KAFKA-1920) Add a metric to count client side errors in BrokerTopicMetrics

[ https://issues.apache.org/jira/browse/KAFKA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1920. -- Resolution: Duplicate Similar metrics are proposed in KAFKA-5746. > Add a metric to count client s

[jira] [Resolved] (KAFKA-1138) Remote producer uses the hostname defined in broker

[ https://issues.apache.org/jira/browse/KAFKA-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1138. -- Resolution: Fixed > Remote producer uses the hostname defined in bro

[jira] [Resolved] (KAFKA-908) Write duplicate messages during broker failure

[ https://issues.apache.org/jira/browse/KAFKA-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-908. - Resolution: Fixed Closing inactive issue. Pl reopen if you think the issue still exists > Write duplic

[jira] [Resolved] (KAFKA-2028) Unable to start the ZK instance after myid file was missing and had to recreate it.

[ https://issues.apache.org/jira/browse/KAFKA-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2028. -- Resolution: Fixed related to config issue. Pl reopen if you think the issue still exists > Unable

[jira] [Resolved] (KAFKA-2343) Clarify KafkaConsumer.poll rebalance behavior

[ https://issues.apache.org/jira/browse/KAFKA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2343. -- Resolution: Fixed Javadocs updated in newer versions. > Clarify KafkaConsumer.poll rebalance behav

[jira] [Resolved] (KAFKA-2750) Sender.java: handleProduceResponse does not check protocol version

[ https://issues.apache.org/jira/browse/KAFKA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2750. -- Resolution: Fixed This was fixed in KAFKA-4462 /KIP-97 for newer clients > Sender.j

[jira] [Resolved] (KAFKA-2842) BrokerEndPoint regex does't support hostname with _

[ https://issues.apache.org/jira/browse/KAFKA-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2842. -- Resolution: Fixed This was fixed in KAFKA-3719 > BrokerEndPoint regex does't support hostn

[jira] [Resolved] (KAFKA-2897) Class NIOServerCnxn$Factory not found due to mismatch in dependencies

[ https://issues.apache.org/jira/browse/KAFKA-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2897. -- Resolution: Won't Fix Closing inactive issue. Pl reopen if you think the issue still exists &g

[jira] [Resolved] (KAFKA-2986) Consumer group doesn't lend itself well for slow consumers with varying message size

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

[jira] [Resolved] (KAFKA-3079) org.apache.kafka.common.KafkaException: java.lang.SecurityException: Configuration Error:

[ https://issues.apache.org/jira/browse/KAFKA-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3079. -- Resolution: Cannot Reproduce Mostly related to config error. Pl reopen if you think the issue still

[jira] [Resolved] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3647. -- Resolution: Fixed Closing as per above comments. > Unable to set a ssl provi

[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 issues w

[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-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.CreateTo

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

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

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

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

dev@kafka.apache.org

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

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

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

[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-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 --create w

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

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

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

[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. > Failed

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

[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

Re: Perf producer/consumers for compacted topics

kafka.log:type=LogCleanerManager,name=max-dirty-percent Manikumar On Tue, May 17, 2016 at 8:45 PM, Tom Crayford wrote: > Hi there, > > As noted in the 0.10.0.0-RC4 release thread, we (Heroku Kafka) have been > doing extensive benchmarking of Kafka. In our case this is to help give &

Apache Kafka JIRA Worflow: Add Closed -> Reopen transition

Jun/Ismail, I requested Apache Infra to change JIRA workflow to add Closed -> Reopen transition. https://issues.apache.org/jira/browse/INFRA-11857 Let me know, If any concerns Manikumar

Re: Apache Kafka JIRA Worflow: Add Closed -> Reopen transition

Hi, There were some jiras which are closed but not resolved. I just wanted to close those jiras properly, so that they won't appear in jira search. Without this new transition i was not able close them properly. Manikumar On May 21, 2016 11:23 AM, "Harsha" wrot

Re: [VOTE] KIP-58 - Make Log Compaction Point Configurable

+1 (non binding) On Wed, May 25, 2016 at 4:03 PM, Tom Crayford wrote: > +1 (non binding) > > Agree on log.cleaner.compaction.delay.ms being the better name. > > I think this setting is going to be extremely hard to tune for users, and > worry about adding yet more configuration - Kafka already h

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

+1 (non-binding) On Fri, Jun 17, 2016 at 3:37 PM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > +1 (non-binding) > > On Fri, Jun 17, 2016 at 4:45 AM, Grant Henke wrote: > > > +1 > > > > On Thu, Jun 16, 2016 at 8:50 PM, tao xiao wrote: > > > > > +1 > > > > > > On Fri, 17 Jun 2016 at 09

Re: [VOTE] KIP-4 Create Topics Schema

+1 (non-binding) On Tue, Jun 21, 2016 at 9:16 AM, Ewen Cheslack-Postava wrote: > +1 (binding) and thanks for the work on this Grant! > > -Ewen > > On Mon, Jun 20, 2016 at 12:18 PM, Gwen Shapira wrote: > > > +1 (binding) > > > > On Mon, Jun 20, 2016 at 12:13 PM, Tom Crayford > > wrote: > > > +1

consumer.subscribe(Pattern p , ..) method fails with Authorizer

$) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized to access topics: [__consumer_offsets] Thanks, Manikumar

Re: [DISCUSS] KIP-4 ACL Admin Schema

Hi, Can we allow ListAcls to take list of resources? This may help when we have many associated resources under same principal. Thanks Manikumar On Fri, Jul 15, 2016 at 11:15 AM, Gwen Shapira wrote: > Thank you, Grant. This is lovely :) > > Few comments / requests for clarificati

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 wrote: > Hello Kafka users, developers and client-developers, > > This is t

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

ka-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-4008). Thanks to Manikumar Reddy for reporting the >&g

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 (lazy > majority) on

[Test Mail] Kafka JIRAs Waiting for Review

[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&focusedCommentId=15880385#comment-15880385 ] Manikumar commented on KAFKA-4788: -- [~ijuma] While using kafka-topics.sh, we are d

[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&focusedCommentId=15880385#comment-15880385 ] Manikumar edited comment on KAFKA-4788 at 2/23/17 1:0

[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&focusedCommentId=15894097#comment-15894097 ] Manikumar commented on KAFKA-4807: -- This is related to KAFKA-

[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&focusedCommentId=15894178#comment-15894178 ] Manikumar commented on KAFKA-4795: -- [~vahid] If we disable topic deletion the

[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&focusedCommentId=15894178#comment-15894178 ] Manikumar edited comment on KAFKA-4795 at 3/3/17 11:2

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