[
https://issues.apache.org/jira/browse/KAFKA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310783#comment-14310783
]
Neha Narkhede commented on KAFKA-1920:
--
[~aauradkar] What sort of client side errors
[
https://issues.apache.org/jira/browse/KAFKA-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310790#comment-14310790
]
Neha Narkhede commented on KAFKA-620:
-
[~guozhang] It does. Feel free to close this as
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1809:
Attachment: KAFKA-1809.v1.patch
For some reason the latest patch generated by patch tool fails to
[
https://issues.apache.org/jira/browse/KAFKA-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-1903.
Zk Expiration causes controller deadlock
[
https://issues.apache.org/jira/browse/KAFKA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310901#comment-14310901
]
Neha Narkhede commented on KAFKA-1908:
--
Thanks for sharing this test case!
bq. A
[
https://issues.apache.org/jira/browse/KAFKA-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310907#comment-14310907
]
Neha Narkhede commented on KAFKA-1792:
--
[~Dmitry Pekar] The last discussion on the
[
https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310912#comment-14310912
]
Jay Kreps commented on KAFKA-1646:
--
Hey guys if this forces full recovery the impact on
[
https://issues.apache.org/jira/browse/KAFKA-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310915#comment-14310915
]
Neha Narkhede commented on KAFKA-1831:
--
[~markap14] The producer has a client.id and
[
https://issues.apache.org/jira/browse/KAFKA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310918#comment-14310918
]
Neha Narkhede commented on KAFKA-313:
-
[~singhashish] We are moving to a centralized
[
https://issues.apache.org/jira/browse/KAFKA-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-1805:
-
Reviewer: Guozhang Wang
[~guozhang] Since you started looking at the patch, would you like to
[
https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1865:
-
Assignee: Jay Kreps
Status: Patch Available (was: Open)
Investigate adding a flush() call to new
[
https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310927#comment-14310927
]
Jay Kreps commented on KAFKA-1865:
--
Created reviewboard
[
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
[
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
[
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
[
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?
[
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
[
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
[
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
[
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
[
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
[
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
[
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).
[
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
[
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
[
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
--
[
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
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
[
https://issues.apache.org/jira/browse/KAFKA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311098#comment-14311098
]
Joe Stein commented on KAFKA-1898:
--
Updated the description. The part that the client
[
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
[
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:
[
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
[
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
[
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
[
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
[
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:
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311139#comment-14311139
]
Manikumar Reddy commented on KAFKA-936:
---
After KAFKA-1481, I am observing one issue.
[
https://issues.apache.org/jira/browse/KAFKA-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311142#comment-14311142
]
Guozhang Wang commented on KAFKA-1794:
--
Makes sense.
Make config and config
[
https://issues.apache.org/jira/browse/KAFKA-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311151#comment-14311151
]
Manikumar Reddy commented on KAFKA-1930:
Are we supporting self-documentation in
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Stein updated KAFKA-1898:
-
Description:
There are a few different scenarios where you want/need to know the
status/state of a
[
https://issues.apache.org/jira/browse/KAFKA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311140#comment-14311140
]
Gwen Shapira commented on KAFKA-1856:
-
Looks good!
[~joestein] or [~nehanarkhede] -
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:
[
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
[
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
[
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
[
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
[
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
[
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
[
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:
[
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
[
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:
[
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
[
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
[
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
[
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
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
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
[
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
[
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.
[
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
[
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
[
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
-
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311109#comment-14311109
]
Gwen Shapira commented on KAFKA-1908:
-
I think its a multi-lan scenario.
The broker
[
https://issues.apache.org/jira/browse/KAFKA-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311136#comment-14311136
]
Guozhang Wang commented on KAFKA-1805:
--
Thanks for the patch [~parth.brahmbhatt],
[
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]
[
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
[
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
[
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?
[
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
[
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
[
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.
-
[
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
[
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
[
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
--
[
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
[
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
-
[
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
[
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
1 - 100 of 146 matches
Mail list logo