[jira] [Updated] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1865: - Summary: Add a flush() call to the new producer API (was: Investigate adding a flush() call to new

[jira] [Updated] (KAFKA-1865) Investigate adding a flush() call to new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1865: - Attachment: KAFKA-1865.patch Investigate adding a flush() call to new producer API

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14310948#comment-14310948 ] Jay Kreps commented on KAFKA-1447: -- Does this problem still exist? Controlled shutdown

[jira] [Commented] (KAFKA-1718) Message Size Too Large error when only small messages produced with Snappy

[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310958#comment-14310958 ] Jay Kreps commented on KAFKA-1718: -- [~junrao], [~guozhang] is this still ongoing?

[jira] [Resolved] (KAFKA-1745) Each new thread creates a PIPE and KQUEUE as open files during producer.send() and does not get cleared when the thread that creates them is cleared.

[ https://issues.apache.org/jira/browse/KAFKA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1745. -- Resolution: Won't Fix Seems to be a problem in Java. Each new thread creates a PIPE and KQUEUE as

[jira] [Resolved] (KAFKA-1657) Fetch request using Simple consumer fails due to failed due to Leader not local for partition

[ https://issues.apache.org/jira/browse/KAFKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1657. -- Resolution: Won't Fix I think the ultimate solution here is to move to the new consumer which should

[jira] [Commented] (KAFKA-1758) corrupt recovery file prevents startup

[ https://issues.apache.org/jira/browse/KAFKA-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310991#comment-14310991 ] Jay Kreps commented on KAFKA-1758: -- This is actually not a very difficult change--in

[jira] [Resolved] (KAFKA-402) Adding handling various kind of exception support at server side

[ https://issues.apache.org/jira/browse/KAFKA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-402. - Resolution: Won't Fix Adding handling various kind of exception support at server side

[jira] [Resolved] (KAFKA-410) after been killed, one broker fail to re-join the cluster after restarted

[ https://issues.apache.org/jira/browse/KAFKA-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-410. - Resolution: Cannot Reproduce after been killed, one broker fail to re-join the cluster after restarted

[jira] [Resolved] (KAFKA-398) Enhance SocketServer to Enable Sending Requests

[ https://issues.apache.org/jira/browse/KAFKA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-398. - Resolution: Won't Fix Enhance SocketServer to Enable Sending Requests

[jira] [Resolved] (KAFKA-462) ZK thread crashing doesn't bring down the broker (and doesn't come back up).

[ https://issues.apache.org/jira/browse/KAFKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-462. - Resolution: Won't Fix ZK thread crashing doesn't bring down the broker (and doesn't come back up).

[jira] [Resolved] (KAFKA-478) Move start_consumer start_producer inside start_entity_in_background

[ https://issues.apache.org/jira/browse/KAFKA-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-478. - Resolution: Won't Fix Move start_consumer start_producer inside start_entity_in_background

[jira] [Resolved] (KAFKA-558) KafkaETLContext should use getTopicMetadata before sending offset requests

[ https://issues.apache.org/jira/browse/KAFKA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-558. - Resolution: Won't Fix KafkaETLContext should use getTopicMetadata before sending offset requests

[jira] [Resolved] (KAFKA-1790) Remote controlled shutdown was removed

[ https://issues.apache.org/jira/browse/KAFKA-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1790. -- Resolution: Won't Fix Remote controlled shutdown was removed --

[jira] [Commented] (KAFKA-1898) compatibility testing framework

[ https://issues.apache.org/jira/browse/KAFKA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311039#comment-14311039 ] Jay Kreps commented on KAFKA-1898: -- [~charmalloc] Can you expand on this ticket, there is

[jira] [Created] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

Jay Kreps created KAFKA-1927: Summary: Replace requests in kafka.api with requests in org.apache.kafka.common.requests Key: KAFKA-1927 URL: https://issues.apache.org/jira/browse/KAFKA-1927 Project: Kafka

[jira] [Resolved] (KAFKA-1290) TestLogCleaning tool hangs on the new producer

[ https://issues.apache.org/jira/browse/KAFKA-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1290. -- Resolution: Fixed Seems to have fixed itself. TestLogCleaning tool hangs on the new producer

[jira] [Updated] (KAFKA-1404) Close unused log file

[ https://issues.apache.org/jira/browse/KAFKA-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1404: - Priority: Major (was: Critical) Close unused log file - Key:

[jira] [Resolved] (KAFKA-674) Clean Shutdown Testing - Log segments checksums mismatch

[ https://issues.apache.org/jira/browse/KAFKA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-674. - Resolution: Invalid Clean Shutdown Testing - Log segments checksums mismatch

[jira] [Commented] (KAFKA-723) Scala's default case class toString() is very inefficient

[ https://issues.apache.org/jira/browse/KAFKA-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310965#comment-14310965 ] Jay Kreps commented on KAFKA-723: - [~nehanarkhede] I think we did this, no? Scala's

[jira] [Comment Edited] (KAFKA-1758) corrupt recovery file prevents startup

[ https://issues.apache.org/jira/browse/KAFKA-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310991#comment-14310991 ] Jay Kreps edited comment on KAFKA-1758 at 2/7/15 11:13 PM: --- This

[jira] [Resolved] (KAFKA-1072) Allow mulitple topics selected with a TopicFilter to be balanced among consumers

[ https://issues.apache.org/jira/browse/KAFKA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1072. -- Resolution: Fixed I think this is solved with the partition.assignment.strategy option in 0.8.2 Allow

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

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1044: - Assignee: (was: Jay Kreps) change log4j to slf4j -- Key:

[jira] [Resolved] (KAFKA-839) Race condition between flushInterval and flushSchedulerInterval

[ https://issues.apache.org/jira/browse/KAFKA-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-839. - Resolution: Won't Fix Race condition between flushInterval and flushSchedulerInterval

[jira] [Commented] (KAFKA-841) Merge the partition and replica state machines into a single unified state machine in the controller

[ https://issues.apache.org/jira/browse/KAFKA-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311021#comment-14311021 ] Jay Kreps commented on KAFKA-841: - [~nehanarkhede] is this still a consideration? Merge

[jira] [Resolved] (KAFKA-182) Set a TCP connection timeout for the SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-182. - Resolution: Fixed Set a TCP connection timeout for the SimpleConsumer

[jira] [Resolved] (KAFKA-874) Migration tool's system tests should use separate server.properties files for 0.7 and 0.8 brokers

[ https://issues.apache.org/jira/browse/KAFKA-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-874. - Resolution: Won't Fix Migration tool's system tests should use separate server.properties files for 0.7

[jira] [Resolved] (KAFKA-875) System test cleanup

[ https://issues.apache.org/jira/browse/KAFKA-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-875. - Resolution: Won't Fix System test cleanup --- Key: KAFKA-875

[jira] [Resolved] (KAFKA-266) Kafka web console

[ https://issues.apache.org/jira/browse/KAFKA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-266. - Resolution: Won't Fix Kafka web console - Key: KAFKA-266

[jira] [Updated] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1927: - Description: The common package introduced a better way of defining requests using a new protocol

[jira] [Resolved] (KAFKA-1314) recurring errors

[ https://issues.apache.org/jira/browse/KAFKA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1314. -- Resolution: Won't Fix Doesn't seem to be under active investigation. recurring errors

[jira] [Updated] (KAFKA-902) Randomize backoff on the clients for metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-902: Labels: newbie (was: ) Randomize backoff on the clients for metadata requests

[jira] [Resolved] (KAFKA-1403) Adding timestamp to kafka index structure

[ https://issues.apache.org/jira/browse/KAFKA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1403. -- Resolution: Won't Fix Adding timestamp to kafka index structure

[jira] [Commented] (KAFKA-1403) Adding timestamp to kafka index structure

[ https://issues.apache.org/jira/browse/KAFKA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310980#comment-14310980 ] Jay Kreps commented on KAFKA-1403: -- Ultimately in order to be accurate the time will

[jira] [Resolved] (KAFKA-971) Handle synchronization in updatemetatdata in KafkaApi better

[ https://issues.apache.org/jira/browse/KAFKA-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-971. - Resolution: Fixed I don't see this in KafkaApis any more. [~junrao] can you reopen if this is still a

[jira] [Resolved] (KAFKA-909) Provide support in the producer to specify a stateful instance of an Encoder, like the consuemr allows with the Decoder

[ https://issues.apache.org/jira/browse/KAFKA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-909. - Resolution: Fixed Fix Version/s: 0.8.2 This is available in the new producer. Provide support in

[jira] [Resolved] (KAFKA-288) java impacted changes from new producer and consumer request format

[ https://issues.apache.org/jira/browse/KAFKA-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-288. - Resolution: Won't Fix java impacted changes from new producer and consumer request format

[jira] [Resolved] (KAFKA-293) Allow to configure all broker ids at once similar to how zookeeper handles server ids

[ https://issues.apache.org/jira/browse/KAFKA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-293. - Resolution: Won't Fix Allow to configure all broker ids at once similar to how zookeeper handles server

[jira] [Resolved] (KAFKA-287) Running a consumer client using scala 2.8 fails

[ https://issues.apache.org/jira/browse/KAFKA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-287. - Resolution: Fixed Running a consumer client using scala 2.8 fails

[jira] [Resolved] (KAFKA-280) change on-disk log layout to {log.dir}/topicname/partitionid

[ https://issues.apache.org/jira/browse/KAFKA-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-280. - Resolution: Won't Fix change on-disk log layout to {log.dir}/topicname/partitionid

[jira] [Resolved] (KAFKA-282) Currently iterated chunk is not cleared during consumer shutdown

[ https://issues.apache.org/jira/browse/KAFKA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-282. - Resolution: Fixed Currently iterated chunk is not cleared during consumer shutdown

[jira] [Resolved] (KAFKA-289) reuse topicdata when sending producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-289. - Resolution: Won't Fix reuse topicdata when sending producerrequest

[jira] [Resolved] (KAFKA-291) Add builder to create configs for consumer and broker

[ https://issues.apache.org/jira/browse/KAFKA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-291. - Resolution: Fixed Add builder to create configs for consumer and broker

[jira] [Created] (KAFKA-1926) Replace kafka.utils.Utils with o.a.k.common.utils.Utils

Jay Kreps created KAFKA-1926: Summary: Replace kafka.utils.Utils with o.a.k.common.utils.Utils Key: KAFKA-1926 URL: https://issues.apache.org/jira/browse/KAFKA-1926 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-170) Support for non-blocking polling on multiple streams

[ https://issues.apache.org/jira/browse/KAFKA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-170. - Resolution: Duplicate This is being solved in the new consumer api. Support for non-blocking polling on

[jira] [Commented] (KAFKA-724) Allow automatic socket.send.buffer from operating system

[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311008#comment-14311008 ] Jay Kreps commented on KAFKA-724: - This is fixed on the old scala clients, but not on the

[jira] [Updated] (KAFKA-724) Allow automatic socket.send.buffer from operating system

[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-724: Labels: newbie (was: ) Allow automatic socket.send.buffer from operating system

[jira] [Resolved] (KAFKA-58) Combine fetch/multifetch and send/multisend

[ https://issues.apache.org/jira/browse/KAFKA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-58. Resolution: Fixed (was: Unresolved) Combine fetch/multifetch and send/multisend

[jira] [Resolved] (KAFKA-333) mirroring - enable non-random partitioning in embedded producer

[ https://issues.apache.org/jira/browse/KAFKA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-333. - Resolution: Invalid mirroring - enable non-random partitioning in embedded producer

[jira] [Resolved] (KAFKA-57) Add an optional acknowledgement in the producer

[ https://issues.apache.org/jira/browse/KAFKA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-57. Resolution: Fixed (was: Unresolved) Add an optional acknowledgement in the producer

[jira] [Resolved] (KAFKA-331) recurrent produce errors

[ https://issues.apache.org/jira/browse/KAFKA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-331. - Resolution: Incomplete recurrent produce errors Key:

[jira] [Resolved] (KAFKA-157) Message may be delivered to incorrect partition incase of semantic partitioning

[ https://issues.apache.org/jira/browse/KAFKA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-157. - Resolution: Fixed Message may be delivered to incorrect partition incase of semantic partitioning

[jira] [Resolved] (KAFKA-5) Continuous log flusher

[ https://issues.apache.org/jira/browse/KAFKA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-5. --- Resolution: Invalid (was: Unresolved) Continuous log flusher -- Key:

[jira] [Resolved] (KAFKA-168) Support locality in consumer partition assignment algorithm

[ https://issues.apache.org/jira/browse/KAFKA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-168. - Resolution: Won't Fix Support locality in consumer partition assignment algorithm

[jira] [Resolved] (KAFKA-1) The log4j appender still uses the SyncProducer API

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1. --- Resolution: Invalid (was: Unresolved) The log4j appender still uses the SyncProducer API

[jira] [Resolved] (KAFKA-1239) New producer checklist

[ https://issues.apache.org/jira/browse/KAFKA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1239. -- Resolution: Fixed New producer checklist -- Key: KAFKA-1239

[jira] [Resolved] (KAFKA-1655) Allow high performance SimpleConsumer use cases to still work with new Kafka 0.9 consumer APIs

[ https://issues.apache.org/jira/browse/KAFKA-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1655. -- Resolution: Invalid Allow high performance SimpleConsumer use cases to still work with new Kafka 0.9

[jira] [Created] (KAFKA-1930) Move server over to new metrics library

Jay Kreps created KAFKA-1930: Summary: Move server over to new metrics library Key: KAFKA-1930 URL: https://issues.apache.org/jira/browse/KAFKA-1930 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-1929) Convert core kafka module to use the errors in org.apache.kafka.common.errors

Jay Kreps created KAFKA-1929: Summary: Convert core kafka module to use the errors in org.apache.kafka.common.errors Key: KAFKA-1929 URL: https://issues.apache.org/jira/browse/KAFKA-1929 Project: Kafka

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310972#comment-14310972 ] Jay Kreps commented on KAFKA-1804: -- The remaining issue is the lack of logging. However

[jira] [Commented] (KAFKA-1638) transient unit test failure UncleanLeaderElectionTest

[ https://issues.apache.org/jira/browse/KAFKA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310982#comment-14310982 ] Jay Kreps commented on KAFKA-1638: -- [~junrao] is this still happening? I haven't seen it.

[jira] [Resolved] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-881. - Resolution: Won't Fix Closing due to ancientness. Kafka broker not respecting log.roll.hours

[jira] [Resolved] (KAFKA-864) bin/kafka-gen-reassignment.sh

[ https://issues.apache.org/jira/browse/KAFKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-864. - Resolution: Duplicate I think this is being pursued on another ticket. bin/kafka-gen-reassignment.sh

[jira] [Resolved] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-493. - Resolution: Incomplete High CPU usage on inactive server -

[jira] [Commented] (KAFKA-1831) Producer does not provide any information about which host the data was sent to

[ https://issues.apache.org/jira/browse/KAFKA-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311042#comment-14311042 ] Jay Kreps commented on KAFKA-1831: -- The new producer returns RecordMetadata on each

[jira] [Resolved] (KAFKA-1831) Producer does not provide any information about which host the data was sent to

[ https://issues.apache.org/jira/browse/KAFKA-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1831. -- Resolution: Fixed I think the new producer fixes this, reopen if you disagree. Producer does not

[jira] [Resolved] (KAFKA-1709) [New Java Producer Potential Deadlock] Producer Deadlock when all messages is being sent to single partition

[ https://issues.apache.org/jira/browse/KAFKA-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1709. -- Resolution: Invalid This didn't turn out to be a deadlock. [New Java Producer Potential Deadlock]

[jira] [Resolved] (KAFKA-1587) Possible Memory Leak when we use Kafka 8.0 Producer for sending messages

[ https://issues.apache.org/jira/browse/KAFKA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1587. -- Resolution: Won't Fix Possible Memory Leak when we use Kafka 8.0 Producer for sending messages

[jira] [Commented] (KAFKA-936) Kafka Metrics Memory Leak

[ https://issues.apache.org/jira/browse/KAFKA-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310961#comment-14310961 ] Jay Kreps commented on KAFKA-936: - [~junrao] Does this issue still exist? Kafka Metrics

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14310973#comment-14310973 ] Jay Kreps commented on KAFKA-1408: -- [~junrao], [~dmitrybugaychenko] is this still active?

[jira] [Updated] (KAFKA-1416) Unify sendMessages/getMessages in unit tests

[ https://issues.apache.org/jira/browse/KAFKA-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1416: - Labels: newbie (was: ) Unify sendMessages/getMessages in unit tests

[jira] [Resolved] (KAFKA-867) producer transaction issue when metrics lib not correct

[ https://issues.apache.org/jira/browse/KAFKA-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-867. - Resolution: Incomplete No follow-up. producer transaction issue when metrics lib not correct

[jira] [Resolved] (KAFKA-865) Mavenize and separate the client.

[ https://issues.apache.org/jira/browse/KAFKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-865. - Resolution: Duplicate Mavenize and separate the client. -

[jira] [Resolved] (KAFKA-715) NumberFormatException in PartitionStateInfo

[ https://issues.apache.org/jira/browse/KAFKA-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-715. - Resolution: Duplicate NumberFormatException in PartitionStateInfo

[jira] [Resolved] (KAFKA-711) NPE in TRUNK broker

[ https://issues.apache.org/jira/browse/KAFKA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-711. - Resolution: Invalid NPE in TRUNK broker --- Key: KAFKA-711

[jira] [Resolved] (KAFKA-662) Create testcases for unclean shut down

[ https://issues.apache.org/jira/browse/KAFKA-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-662. - Resolution: Fixed Create testcases for unclean shut down --

[jira] [Resolved] (KAFKA-663) Add deploy feature to System Test

[ https://issues.apache.org/jira/browse/KAFKA-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-663. - Resolution: Won't Fix Not under active development. Add deploy feature to System Test

[jira] [Resolved] (KAFKA-321) Remove dead brokers from ProducerPool

[ https://issues.apache.org/jira/browse/KAFKA-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-321. - Resolution: Fixed Remove dead brokers from ProducerPool -

[jira] [Resolved] (KAFKA-299) Change broker request and response to use Seqs rather than Array

[ https://issues.apache.org/jira/browse/KAFKA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-299. - Resolution: Fixed Change broker request and response to use Seqs rather than Array

[jira] [Resolved] (KAFKA-260) Add audit trail to kafka

[ https://issues.apache.org/jira/browse/KAFKA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-260. - Resolution: Won't Fix Add audit trail to kafka Key: KAFKA-260

[jira] [Resolved] (KAFKA-665) Outgoing responses delayed on a busy Kafka broker

[ https://issues.apache.org/jira/browse/KAFKA-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-665. - Resolution: Fixed We solved this by making the response queue unbounded. When the request queue is full

[jira] [Resolved] (KAFKA-904) ClientUtils throws SocketTimeOut in client side at high load

[ https://issues.apache.org/jira/browse/KAFKA-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-904. - Resolution: Duplicate ClientUtils throws SocketTimeOut in client side at high load

[jira] [Commented] (KAFKA-948) ISR list in LeaderAndISR path not updated for partitions when Broker (which is not leader) is down

[ https://issues.apache.org/jira/browse/KAFKA-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310986#comment-14310986 ] Jay Kreps commented on KAFKA-948: - [~junrao] Can this be closed? ISR list in LeaderAndISR

[jira] [Commented] (KAFKA-783) Preferred replica assignment on leader failure may not be correct

[ https://issues.apache.org/jira/browse/KAFKA-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311002#comment-14311002 ] Jay Kreps commented on KAFKA-783: - [~nehanarkhede] Still a problem? Preferred replica

[jira] [Resolved] (KAFKA-185) The files in the kafka\clients\csharp\src\Kafka\Kafka.Client\cfg folder of the csharp client are out of date.

[ https://issues.apache.org/jira/browse/KAFKA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-185. - Resolution: Invalid The files in the kafka\clients\csharp\src\Kafka\Kafka.Client\cfg folder of the

[jira] [Resolved] (KAFKA-178) Simplify the brokerinfo argument to the producer-perf-test.sh

[ https://issues.apache.org/jira/browse/KAFKA-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-178. - Resolution: Invalid Simplify the brokerinfo argument to the producer-perf-test.sh

[jira] [Resolved] (KAFKA-1827) Optimistic Locking when Producing Messages

[ https://issues.apache.org/jira/browse/KAFKA-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1827. -- Resolution: Won't Fix Yeah this is interesting but currently out of scope. Optimistic Locking when

[jira] [Created] (KAFKA-1928) Move kafka.network over to using the network classes in org.apache.kafka.common.network

Jay Kreps created KAFKA-1928: Summary: Move kafka.network over to using the network classes in org.apache.kafka.common.network Key: KAFKA-1928 URL: https://issues.apache.org/jira/browse/KAFKA-1928

[jira] [Resolved] (KAFKA-479) ZK EPoll taking 100% CPU usage with Kafka Client

[ https://issues.apache.org/jira/browse/KAFKA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-479. - Resolution: Invalid I think we decided this was a java bug. ZK EPoll taking 100% CPU usage with Kafka

[jira] [Updated] (KAFKA-1926) Replace kafka.utils.Utils with o.a.k.common.utils.Utils

[ https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1926: - Description: There is currently a lot of duplication between the Utils class in common and the one in

[jira] [Updated] (KAFKA-1926) Replace kafka.utils.Utils with o.a.k.common.utils.Utils

[ https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1926: - Labels: newbie (was: ) Replace kafka.utils.Utils with o.a.k.common.utils.Utils

[jira] [Commented] (KAFKA-1155) Kafka server can miss zookeeper watches during long zkclient callbacks

[ https://issues.apache.org/jira/browse/KAFKA-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310955#comment-14310955 ] Jay Kreps commented on KAFKA-1155: -- [~nehanarkhede] is this still a problem? Seems like a

[jira] [Resolved] (KAFKA-1145) Broker fail to sync after restart

[ https://issues.apache.org/jira/browse/KAFKA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1145. -- Resolution: Won't Fix Closing since no follow-up. Broker fail to sync after restart

[jira] [Resolved] (KAFKA-1132) Reduce size and amount of server access logs

[ https://issues.apache.org/jira/browse/KAFKA-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1132. -- Resolution: Won't Fix Reduce size and amount of server access logs

[jira] [Commented] (KAFKA-902) Randomize backoff on the clients for metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310963#comment-14310963 ] Jay Kreps commented on KAFKA-902: - This could be accomplished by just adding +/-5 to the

[jira] [Resolved] (KAFKA-1423) Updating partition count clears topic configuration and any further alters done to a topics config do not stick

[ https://issues.apache.org/jira/browse/KAFKA-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1423. -- Resolution: Fixed Fix Version/s: 0.8.2 Updating partition count clears topic configuration and

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

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310994#comment-14310994 ] Jay Kreps commented on KAFKA-1044: -- This would be nice to do. If anyone wants to take it

[jira] [Resolved] (KAFKA-1050) Support for no data loss mode

[ https://issues.apache.org/jira/browse/KAFKA-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1050. -- Resolution: Fixed I think both of these are done on other tickets. Support for no data loss mode

[jira] [Resolved] (KAFKA-744) Bad response time for fetch request

[ https://issues.apache.org/jira/browse/KAFKA-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-744. - Resolution: Invalid Ancient. Bad response time for fetch request ---

[jira] [Resolved] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

[ https://issues.apache.org/jira/browse/KAFKA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-406. - Resolution: Won't Fix Gzipped payload is a fully wrapped Message (with headers), not just payload

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