[jira] [Resolved] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6762. Resolution: Duplicate Duplicate of KAFKA-6854. > log-cleaner thread terminates due to

[jira] [Resolved] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6965. Resolution: Not A Bug > log4j:WARN log messages printed when running kafka-console-producer OOB >

[jira] [Resolved] (KAFKA-6760) responses not logged properly in controller

[ https://issues.apache.org/jira/browse/KAFKA-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6760. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 > responses not logged

[jira] [Resolved] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6973. Resolution: Fixed Fix Version/s: 2.0.0 > setting invalid timestamp causes Kafka broker

[jira] [Created] (KAFKA-6956) Use Java AdminClient in BrokerApiVersionsCommand

Ismael Juma created KAFKA-6956: -- Summary: Use Java AdminClient in BrokerApiVersionsCommand Key: KAFKA-6956 URL: https://issues.apache.org/jira/browse/KAFKA-6956 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6955) Use Java AdminClient in DeleteRecordsCommand

Ismael Juma created KAFKA-6955: -- Summary: Use Java AdminClient in DeleteRecordsCommand Key: KAFKA-6955 URL: https://issues.apache.org/jira/browse/KAFKA-6955 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-6930) Update KafkaZkClient debug log

[ https://issues.apache.org/jira/browse/KAFKA-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6930. Resolution: Fixed > Update KafkaZkClient debug log > -- > >

[jira] [Resolved] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3665. Resolution: Fixed > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Reopened] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3665: > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Resolved] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6873. Resolution: Not A Problem > Broker is not returning data including requested offset >

[jira] [Created] (KAFKA-6923) Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Ismael Juma created KAFKA-6923: -- Summary: Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer Key: KAFKA-6923 URL: https://issues.apache.org/jira/browse/KAFKA-6923 Project:

[jira] [Created] (KAFKA-6921) Remove old Scala producer and all related code, tests, and tools

Ismael Juma created KAFKA-6921: -- Summary: Remove old Scala producer and all related code, tests, and tools Key: KAFKA-6921 URL: https://issues.apache.org/jira/browse/KAFKA-6921 Project: Kafka

[jira] [Resolved] (KAFKA-5907) Support aggregatedJavadoc in Java 9

[ https://issues.apache.org/jira/browse/KAFKA-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5907. Resolution: Fixed [~omkreddy] It does seem to work now, so will mark it as resolved. > Support

[jira] [Resolved] (KAFKA-6828) Index files are no longer sparse in Java 9/10 due to OpenJDK regression

[ https://issues.apache.org/jira/browse/KAFKA-6828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6828. Resolution: Fixed Great! Let's close this then. > Index files are no longer sparse in Java 9/10

[jira] [Resolved] (KAFKA-6879) Controller deadlock following session expiration

[ https://issues.apache.org/jira/browse/KAFKA-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6879. Resolution: Fixed > Controller deadlock following session expiration >

[jira] [Resolved] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6390. Resolution: Fixed > Update ZooKeeper to 3.4.11, Gradle and other minor updates >

[jira] [Reopened] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-4041: > kafka unable to reconnect to zookeeper behind an ELB >

[jira] [Resolved] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6853. Resolution: Fixed > ResponseMetadata calculates latency incorrectly (and therefore >

[jira] [Resolved] (KAFKA-6855) Kafka fails to start due to faulty Java version detection

[ https://issues.apache.org/jira/browse/KAFKA-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6855. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 Thanks for the report. This

[jira] [Resolved] (KAFKA-6796) Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas

[ https://issues.apache.org/jira/browse/KAFKA-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6796. Resolution: Fixed Fix Version/s: 1.2.0 > Surprising UNKNOWN_TOPIC error for produce/fetch

[jira] [Reopened] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-2334: > Prevent HW from going back during leader failover >

[jira] [Created] (KAFKA-6772) Broker should load credentials from ZK before requests are allowed

Ismael Juma created KAFKA-6772: -- Summary: Broker should load credentials from ZK before requests are allowed Key: KAFKA-6772 URL: https://issues.apache.org/jira/browse/KAFKA-6772 Project: Kafka

[jira] [Created] (KAFKA-6763) Consider using direct byte buffers in SslTransportLayer

Ismael Juma created KAFKA-6763: -- Summary: Consider using direct byte buffers in SslTransportLayer Key: KAFKA-6763 URL: https://issues.apache.org/jira/browse/KAFKA-6763 Project: Kafka Issue

[jira] [Reopened] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-6390: > Update ZooKeeper to 3.4.11, Gradle and other minor updates >

[jira] [Resolved] (KAFKA-6683) ReplicaFetcher crashes with "Attempted to complete a transaction which was not started"

[ https://issues.apache.org/jira/browse/KAFKA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6683. Resolution: Fixed Fix Version/s: 1.1.0 > ReplicaFetcher crashes with "Attempted to complete

[jira] [Resolved] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

[ https://issues.apache.org/jira/browse/KAFKA-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4974. Resolution: Fixed > System test failure in 0.8.2.2 upgrade tests >

[jira] [Created] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

Ismael Juma created KAFKA-6616: -- Summary: kafka-merge-pr.py should use GitHub's REST API to merge Key: KAFKA-6616 URL: https://issues.apache.org/jira/browse/KAFKA-6616 Project: Kafka Issue

[jira] [Resolved] (KAFKA-6430) Improve Kafka GZip compression performance

[ https://issues.apache.org/jira/browse/KAFKA-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6430. Resolution: Fixed Fix Version/s: 1.1.0 > Improve Kafka GZip compression performance >

[jira] [Resolved] (KAFKA-6464) Base64URL encoding under JRE 1.7 is broken due to incorrect padding assumption

[ https://issues.apache.org/jira/browse/KAFKA-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6464. Resolution: Fixed Reviewer: Rajini Sivaram (was: Ismael Juma) > Base64URL encoding under JRE

[jira] [Resolved] (KAFKA-6307) mBeanName should be removed before returning from JmxReporter#removeAttribute()

[ https://issues.apache.org/jira/browse/KAFKA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6307. Resolution: Fixed Fix Version/s: 1.1.0 > mBeanName should be removed before returning from

[jira] [Resolved] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2729. Resolution: Fixed Assignee: Onur Karaman Fix Version/s: 1.1.0 We believe this is

[jira] [Resolved] (KAFKA-6320) move ZK metrics in KafkaHealthCheck to ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6320. Resolution: Fixed > move ZK metrics in KafkaHealthCheck to ZookeeperClient >

[jira] [Resolved] (KAFKA-3496) Add reconnect attemps policies for client

[ https://issues.apache.org/jira/browse/KAFKA-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3496. Resolution: Won't Fix We decided to add configs for enabling exponential backoff instead. > Add

[jira] [Resolved] (KAFKA-5895) Gradle 3.0+ is needed on the build

[ https://issues.apache.org/jira/browse/KAFKA-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5895. Resolution: Fixed Fix Version/s: 1.1.0 > Gradle 3.0+ is needed on the build >

[jira] [Resolved] (KAFKA-6331) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6331. Resolution: Fixed Fix Version/s: 1.1.0 > Transient failure in >

[jira] [Created] (KAFKA-6390) Update ZooKeeper to 3.4.11 and other minor updates

Ismael Juma created KAFKA-6390: -- Summary: Update ZooKeeper to 3.4.11 and other minor updates Key: KAFKA-6390 URL: https://issues.apache.org/jira/browse/KAFKA-6390 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-5631) Use Jackson for serialising to JSON

[ https://issues.apache.org/jira/browse/KAFKA-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5631. Resolution: Fixed > Use Jackson for serialising to JSON > --- > >

[jira] [Resolved] (KAFKA-6319) kafka-acls regression for comma characters (and maybe other characters as well)

[ https://issues.apache.org/jira/browse/KAFKA-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6319. Resolution: Fixed > kafka-acls regression for comma characters (and maybe other characters as >

[jira] [Resolved] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6194. Resolution: Fixed Assignee: Ismael Juma Fix Version/s: 1.1.0 I believe this was

[jira] [Resolved] (KAFKA-6075) Kafka cannot recover after an unclean shutdown on Windows

[ https://issues.apache.org/jira/browse/KAFKA-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6075. Resolution: Fixed Assignee: Ismael Juma Fix Version/s: 1.1.0 I believe this was

[jira] [Resolved] (KAFKA-6322) Error deleting log for topic, all log dirs failed.

[ https://issues.apache.org/jira/browse/KAFKA-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6322. Resolution: Fixed Assignee: Ismael Juma I believe this was fixed by KAFKA-6324, please reopen

[jira] [Created] (KAFKA-6332) Kafka system tests should use nc instead of log grep to detect start-up

Ismael Juma created KAFKA-6332: -- Summary: Kafka system tests should use nc instead of log grep to detect start-up Key: KAFKA-6332 URL: https://issues.apache.org/jira/browse/KAFKA-6332 Project: Kafka

[jira] [Created] (KAFKA-6330) KafkaZkClient request queue time metric

Ismael Juma created KAFKA-6330: -- Summary: KafkaZkClient request queue time metric Key: KAFKA-6330 URL: https://issues.apache.org/jira/browse/KAFKA-6330 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6324) Change LogSegment.delete to deleteIfExists and harden log recovery

Ismael Juma created KAFKA-6324: -- Summary: Change LogSegment.delete to deleteIfExists and harden log recovery Key: KAFKA-6324 URL: https://issues.apache.org/jira/browse/KAFKA-6324 Project: Kafka

[jira] [Resolved] (KAFKA-6313) Kafka Core should have explicit SLF4J API dependency

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6313. Resolution: Fixed > Kafka Core should have explicit SLF4J API dependency >

[jira] [Resolved] (KAFKA-6065) Add ZooKeeperRequestLatencyMs to KafkaZkClient

[ https://issues.apache.org/jira/browse/KAFKA-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6065. Resolution: Fixed > Add ZooKeeperRequestLatencyMs to KafkaZkClient >

[jira] [Created] (KAFKA-6317) Maven artifact for kafka should not depend on log4j

Ismael Juma created KAFKA-6317: -- Summary: Maven artifact for kafka should not depend on log4j Key: KAFKA-6317 URL: https://issues.apache.org/jira/browse/KAFKA-6317 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-6174) Add methods in Options classes to keep binary compatibility with 0.11

[ https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6174. Resolution: Fixed Fix Version/s: 1.1.0 > Add methods in Options classes to keep binary

[jira] [Resolved] (KAFKA-2188) JBOD Support

[ https://issues.apache.org/jira/browse/KAFKA-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2188. Resolution: Duplicate KIP-112 and KIP-113 replaced this one. > JBOD Support > > >

[jira] [Created] (KAFKA-6261) Request logging throws exception if acks=0

Ismael Juma created KAFKA-6261: -- Summary: Request logging throws exception if acks=0 Key: KAFKA-6261 URL: https://issues.apache.org/jira/browse/KAFKA-6261 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1044. Resolution: Fixed Fix Version/s: 1.1.0 > change log4j to slf4j > -- > >

[jira] [Resolved] (KAFKA-4871) Kafka doesn't respect TTL on Zookeeper hostname - crash if zookeeper IP changes

[ https://issues.apache.org/jira/browse/KAFKA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4871. Resolution: Duplicate Duplicate of KAFKA-5473. > Kafka doesn't respect TTL on Zookeeper hostname -

[jira] [Resolved] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4041. Resolution: Fixed Marking as a duplicate of KAFKA-5473. In that JIRA, we will recreate the

[jira] [Reopened] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-4041: > kafka unable to reconnect to zookeeper behind an ELB >

[jira] [Resolved] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4041. Resolution: Duplicate > kafka unable to reconnect to zookeeper behind an ELB >

[jira] [Resolved] (KAFKA-2193) Intermittent network + DNS issues can cause brokers to permanently drop out of a cluster

[ https://issues.apache.org/jira/browse/KAFKA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2193. Resolution: Duplicate Duplicate of KAFKA-5473. > Intermittent network + DNS issues can cause

[jira] [Resolved] (KAFKA-2864) Bad zookeeper host causes broker to shutdown uncleanly and stall producers

[ https://issues.apache.org/jira/browse/KAFKA-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2864. Resolution: Duplicate Duplicate of KAFKA-5473. > Bad zookeeper host causes broker to shutdown

[jira] [Resolved] (KAFKA-6247) Fix system test dependency issues

[ https://issues.apache.org/jira/browse/KAFKA-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6247. Resolution: Fixed Assignee: Colin P. McCabe Fix Version/s: 1.1.0 > Fix system test

[jira] [Resolved] (KAFKA-6223) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/KAFKA-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6223. Resolution: Fixed > Please delete old releases from mirroring system >

[jira] [Resolved] (KAFKA-6103) one broker appear to dead lock after running serval hours with a fresh cluster

[ https://issues.apache.org/jira/browse/KAFKA-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6103. Resolution: Duplicate > one broker appear to dead lock after running serval hours with a fresh

[jira] [Resolved] (KAFKA-6046) DeleteRecordsRequest to a non-leader

[ https://issues.apache.org/jira/browse/KAFKA-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6046. Resolution: Fixed > DeleteRecordsRequest to a non-leader > > >

[jira] [Resolved] (KAFKA-679) Phabricator for code review

[ https://issues.apache.org/jira/browse/KAFKA-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-679. --- Resolution: Won't Do Yes, this can be safely closed. > Phabricator for code review >

[jira] [Resolved] (KAFKA-1408) Kafk broker can not stop itself normaly after problems with connection to ZK

[ https://issues.apache.org/jira/browse/KAFKA-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1408. Resolution: Duplicate Closing as duplicate of KAFKA-1317 based on other comments and the fact that

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

[ https://issues.apache.org/jira/browse/KAFKA-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-1993: > Enable topic deletion as default > > > Key:

[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 ] Ismael Juma resolved KAFKA-1993. Resolution: Duplicate > Enable topic deletion as default > > >

[jira] [Resolved] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command

[ https://issues.apache.org/jira/browse/KAFKA-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4675. Resolution: Duplicate KAFKA-6098 is the same issue and has more information. > Subsequent

[jira] [Resolved] (KAFKA-6210) IllegalArgumentException if 1.0.0 is used for inter.broker.protocol.version or log.message.format.version

[ https://issues.apache.org/jira/browse/KAFKA-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6210. Resolution: Fixed > IllegalArgumentException if 1.0.0 is used for inter.broker.protocol.version >

[jira] [Created] (KAFKA-6210) IllegalArgumentException if 1.0.0 is used for inter.broker.protocol.version or log.message.format.version

Ismael Juma created KAFKA-6210: -- Summary: IllegalArgumentException if 1.0.0 is used for inter.broker.protocol.version or log.message.format.version Key: KAFKA-6210 URL:

[jira] [Resolved] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6185. Resolution: Fixed > Selector memory leak with high likelihood of OOM in case of down conversion >

[jira] [Resolved] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6146. Resolution: Fixed > minimize the number of triggers enqueuing PreferredReplicaLeaderElection >

[jira] [Resolved] (KAFKA-1506) Cancel "kafka-reassign-partitions" Job

[ https://issues.apache.org/jira/browse/KAFKA-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1506. Resolution: Duplicate Marking as a duplicate of KAFKA-1676 as the latter contains more information.

[jira] [Reopened] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3917: If you're running 0.10.2.0, then potentially KAFKA-5413, but I'll reopen until we can verify. > Some

[jira] [Resolved] (KAFKA-2616) Improve Kakfa client exceptions

[ https://issues.apache.org/jira/browse/KAFKA-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2616. Resolution: Auto Closed BlockingChannel is only used by the Scala clients. which are no longer

[jira] [Resolved] (KAFKA-2636) Producer connectivity obscured connection failure logging

[ https://issues.apache.org/jira/browse/KAFKA-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2636. Resolution: Not A Problem The producer should throw a TimeoutException to the callback or if

[jira] [Resolved] (KAFKA-2662) Make ConsumerIterator thread-safe for multiple threads in different Kafka groups

[ https://issues.apache.org/jira/browse/KAFKA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2662. Resolution: Auto Closed The Scala consumers are no longer supported. Please upgrade to the Java

[jira] [Resolved] (KAFKA-2725) high level consumer rebalances with auto-commit disabled should throw an exception

[ https://issues.apache.org/jira/browse/KAFKA-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2725. Resolution: Auto Closed The Scala consumers are no longer supported. If this still applies to the

[jira] [Resolved] (KAFKA-3071) Kafka Server 0.8.2 ERROR OOME with siz

[ https://issues.apache.org/jira/browse/KAFKA-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3071. Resolution: Auto Closed The SimpleConsumer is no longer supported and will be removed in a future

[jira] [Resolved] (KAFKA-3860) No broker partitions consumed by consumer thread

[ https://issues.apache.org/jira/browse/KAFKA-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3860. Resolution: Auto Closed The old consumer is no longer supported, please upgrade to the Java

[jira] [Resolved] (KAFKA-3756) javadoc has issues with incorrect @param, @throws, @return

[ https://issues.apache.org/jira/browse/KAFKA-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3756. Resolution: Auto Closed Closing as 0.8.2 branch is no longer supported. > javadoc has issues with

[jira] [Resolved] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3917. Resolution: Duplicate This log cleaner issue has been fixed in more recent versions. I suggest

[jira] [Resolved] (KAFKA-4096) Kafka Backup and Recovery

[ https://issues.apache.org/jira/browse/KAFKA-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4096. Resolution: Auto Closed Thanks for the JIRA. This should work. If you are still seeing this with a

[jira] [Resolved] (KAFKA-4832) kafka producer send Async message to the wrong IP cannot to stop producer.close()

[ https://issues.apache.org/jira/browse/KAFKA-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4832. Resolution: Auto Closed The Scala producers have been deprecated for a while and no further work is

[jira] [Resolved] (KAFKA-5963) Null Pointer Exception on server

[ https://issues.apache.org/jira/browse/KAFKA-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5963. Resolution: Auto Closed Thanks for the JIRA. Kafka 0.8.x is no longer supported and the issue has

[jira] [Resolved] (KAFKA-5981) Update the affected versions on bug KAFKA-1194

[ https://issues.apache.org/jira/browse/KAFKA-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5981. Resolution: Duplicate Updated the fix versions. Only included the ones that are still supported. >

[jira] [Resolved] (KAFKA-6043) Kafka 8.1.1 - .ZookeeperConsumerConnector.shutdown(ZookeeperConsumerConnector.scala:110) blocked

[ https://issues.apache.org/jira/browse/KAFKA-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6043. Resolution: Auto Closed The old consumer is deprecated and no further changes are planned. Please

[jira] [Resolved] (KAFKA-6117) One Broker down can't rejoin the cluster

[ https://issues.apache.org/jira/browse/KAFKA-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6117. Resolution: Auto Closed Thanks for the JIRA. 0.8.2.x is unsupported at this point. Newer releases

[jira] [Resolved] (KAFKA-5934) Cross build for scala 2.12

[ https://issues.apache.org/jira/browse/KAFKA-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5934. Resolution: Won't Fix Thanks for the JIRA and PR. 0.8.x is unsupported at this point and we don't

[jira] [Resolved] (KAFKA-2156) Possibility to plug in custom MetricRegistry

[ https://issues.apache.org/jira/browse/KAFKA-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2156. Resolution: Auto Closed It's unlikely that we will do this for Yammer Metrics. Please file a

[jira] [Resolved] (KAFKA-2180) topics never create on brokers though it succeeds in tool and is in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2180. Resolution: Auto Closed Not enough information and very old so auto closing. > topics never create

[jira] [Resolved] (KAFKA-2222) Write "Input/output error" did not result in broker shutdown

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-. Resolution: Won't Fix The code changed dramatically since this was filed (the stacktrace doesn't

[jira] [Resolved] (KAFKA-6064) Cluster hung when the controller tried to delete a bunch of topics

[ https://issues.apache.org/jira/browse/KAFKA-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6064. Resolution: Auto Closed 0.8.2.1 is no longer supported. Many bugs related to topic deletion have

[jira] [Created] (KAFKA-6136) Transient test failure: SaslPlainSslEndToEndAuthorizationTest.testTwoConsumersWithDifferentSaslCredentials

Ismael Juma created KAFKA-6136: -- Summary: Transient test failure: SaslPlainSslEndToEndAuthorizationTest.testTwoConsumersWithDifferentSaslCredentials Key: KAFKA-6136 URL:

[jira] [Resolved] (KAFKA-6131) Transaction markers are sometimes discarded if txns complete concurrently

[ https://issues.apache.org/jira/browse/KAFKA-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6131. Resolution: Fixed Fix Version/s: 1.1.0 0.11.0.2 1.0.0

[jira] [Resolved] (KAFKA-6128) Shutdown script does not do a clean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6128. Resolution: Not A Problem > Shutdown script does not do a clean shutdown >

[jira] [Reopened] (KAFKA-6128) Shutdown script does not do a clean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-6128: > Shutdown script does not do a clean shutdown > > >

[jira] [Resolved] (KAFKA-6116) Major performance issue due to excessive logging during leader election

[ https://issues.apache.org/jira/browse/KAFKA-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6116. Resolution: Fixed Fixed in 0.11.0, 1.0 and trunk. Commit for 0.11.0:

[jira] [Created] (KAFKA-6116) Major performance issue due to excessive logging during leader election

Ismael Juma created KAFKA-6116: -- Summary: Major performance issue due to excessive logging during leader election Key: KAFKA-6116 URL: https://issues.apache.org/jira/browse/KAFKA-6116 Project: Kafka

[jira] [Created] (KAFKA-6111) Tests for KafkaControllerZkUtils

Ismael Juma created KAFKA-6111: -- Summary: Tests for KafkaControllerZkUtils Key: KAFKA-6111 URL: https://issues.apache.org/jira/browse/KAFKA-6111 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-6070) ducker-ak: add ipaddress and enum34 dependencies to docker image

[ https://issues.apache.org/jira/browse/KAFKA-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6070. Resolution: Fixed Fix Version/s: 1.1.0 1.0.0 > ducker-ak: add ipaddress

[jira] [Resolved] (KAFKA-5720) In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5720. Resolution: Fixed Fix Version/s: (was: 1.1.0) 1.0.0 > In Jenkins,

<    1   2   3   4   5   6   7   8   9   10   >