[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527084#comment-13527084
]
Joel Koshy commented on KAFKA-597:
--
On daemon vs non-daemon and shutdown vs shutdownNow. I
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-646:
Attachment: kafka-646-patch-num1-v2.patch
Attached patch v2.
The changes from patch v1:
1. Deleted
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527078#comment-13527078
]
Swapnil Ghike edited comment on KAFKA-646 at 12/8/12 6:17 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527039#comment-13527039
]
Joel Koshy commented on KAFKA-664:
--
+1
Some minor comments:
- We can probably remove the
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-597:
Attachment: KAFKA-597-v5.patch
Thanks, new patch v5 addresses your comments:
- Improved javadoc
- This is ac
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527019#comment-13527019
]
Swapnil Ghike commented on KAFKA-646:
-
Actually I just realized that the Aggregated*Sta
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-664:
Attachment: watchersForKey.png
kafka-664-draft.patch
The problem was ever increasing
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526973#comment-13526973
]
Neha Narkhede edited comment on KAFKA-664 at 12/8/12 1:56 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526966#comment-13526966
]
Joel Koshy commented on KAFKA-597:
--
I haven't fully reviewed, but a couple of initial comm
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-646:
Attachment: kafka-646-patch-num1-v1.patch
This patch has a bunch of refactoring changes and a couple
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-644:
Attachment: kafka-644-v2.patch
Uploaded kafka-644-v2.patch which supports the property "auto_create_topic"
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526887#comment-13526887
]
Jay Kreps commented on KAFKA-664:
-
Another issue is that we are saving the full producer re
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526883#comment-13526883
]
Joel Koshy commented on KAFKA-664:
--
Okay I'm slightly confused. Even on expiration the req
[
https://issues.apache.org/jira/browse/KAFKA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-636:
Attachment: KAFKA-636-v1.patch
This patch implements asynchronous delete in the log.
To do this Log.scala n
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526876#comment-13526876
]
Joel Koshy commented on KAFKA-664:
--
To clarify, the map itself shouldn't grow indefinitely
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-597:
Attachment: KAFKA-597-v4.patch
Patch v4.
- Rebased
- Makes use of thread factory
- Fixed broken scaladoc
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-644.
---
> System Test should run properly with mixed File System Pathname
> --
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-644:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> System Test should run prop
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526851#comment-13526851
]
Neha Narkhede commented on KAFKA-644:
-
+1. Thanks for the patch !
> Sy
[
https://issues.apache.org/jira/browse/KAFKA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-666:
Description:
I've seen that fetch requests from the replicas take several seconds to
complete. The
Neha Narkhede created KAFKA-666:
---
Summary: Fetch requests from the replicas take several seconds to
complete on the leader
Key: KAFKA-666
URL: https://issues.apache.org/jira/browse/KAFKA-666
Project: Ka
Neha Narkhede created KAFKA-665:
---
Summary: Outgoing responses delayed on a busy Kafka broker
Key: KAFKA-665
URL: https://issues.apache.org/jira/browse/KAFKA-665
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526808#comment-13526808
]
Neha Narkhede commented on KAFKA-664:
-
The root cause seems to be that watchersForKey m
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps reassigned KAFKA-664:
---
Assignee: Jay Kreps
> Kafka server threads die due to OOME during long running test
>
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526805#comment-13526805
]
Jay Kreps commented on KAFKA-664:
-
Looks like the problem is in request purgatory--watchers
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526720#comment-13526720
]
Neha Narkhede commented on KAFKA-664:
-
I'm re-running the tests with that option now
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526719#comment-13526719
]
Neha Narkhede commented on KAFKA-664:
-
Heap dump is here -
http://people.apache.org/~n
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526713#comment-13526713
]
Jay Kreps commented on KAFKA-664:
-
One pain of oom is that the thing leaking the memory is
[
https://issues.apache.org/jira/browse/KAFKA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526687#comment-13526687
]
David Arthur commented on KAFKA-657:
I have started a wiki page for this design discuss
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526624#comment-13526624
]
David Arthur commented on KAFKA-374:
Not sure how you guys feel about having Java in th
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526624#comment-13526624
]
David Arthur edited comment on KAFKA-374 at 12/7/12 6:38 PM:
-
N
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-374:
---
Comment: was deleted
(was: Pure-java crc32 taken from Hadoop)
> Move to java CRC32 implementation
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-374:
---
Attachment: KAFKA-374.patch
Pure-java crc32 taken from Hadoop
> Move to java CRC32 im
[
https://issues.apache.org/jira/browse/KAFKA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-651:
Status: Patch Available (was: Open)
> Create testcases on auto create topics
>
[
https://issues.apache.org/jira/browse/KAFKA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-651:
Attachment: kafka-651-v1.patch
Uploaded kafka-651-v1.patch with 1 testcase to cover each functional group:
t
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526590#comment-13526590
]
Neha Narkhede commented on KAFKA-664:
-
Another observation - The server is probably GCi
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-664:
Attachment: thread-dump.log
Attaching a thread dump that shows -
1. 4 processor threads and the acc
Neha Narkhede created KAFKA-664:
---
Summary: Kafka server threads die due to OOME during long running
test
Key: KAFKA-664
URL: https://issues.apache.org/jira/browse/KAFKA-664
Project: Kafka
Issu
Ben,
I would try to run DumpLogSegments to check if the server's data is
not corrupted due to a bug in the producer.
Thanks,
Neha
On Fri, Dec 7, 2012 at 7:17 AM, ben fleis wrote:
> I was testing my own code, and using the console consumer against my
> seemingly-working-producer code. Since the
[
https://issues.apache.org/jira/browse/KAFKA-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-662:
Issue Type: Task (was: Bug)
> Create testcases for unclean shut down
>
John Fung created KAFKA-663:
---
Summary: Add "deploy" feature to System Test
Key: KAFKA-663
URL: https://issues.apache.org/jira/browse/KAFKA-663
Project: Kafka
Issue Type: Task
Reporter:
John Fung created KAFKA-662:
---
Summary: Create testcases for unclean shut down
Key: KAFKA-662
URL: https://issues.apache.org/jira/browse/KAFKA-662
Project: Kafka
Issue Type: Bug
Reporter
I was testing my own code, and using the console consumer against my
seemingly-working-producer code. Since the last update, the console
consumer crashes. I am going to try to track it down in the debugger and
will come back with a patch if found.
Command line:
KAFKA_OPTS="-Xmx512M -server
-Dlog
Dah. Misfire. Please ignore if this makes it to an inbox ;)
-b
On Fri, Dec 7, 2012 at 4:13 PM, ben fleis wrote:
> So I was testing my own code, and using the console consumer against my
> seemingly-working-producer code. Since the last update, the console
> consumer crashes. I am going to
So I was testing my own code, and using the console consumer against my
seemingly-working-producer code. Since the last update, the console
consumer crashes. I am going to try to track it down in the debugger and
will come back with a patch if found.
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526440#comment-13526440
]
antoine vianey edited comment on KAFKA-581 at 12/7/12 3:11 PM:
--
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526440#comment-13526440
]
antoine vianey edited comment on KAFKA-581 at 12/7/12 3:11 PM:
--
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
antoine vianey updated KAFKA-581:
-
Attachment: zookeeper-server-stop.bat
kafka-server-stop.bat
Can you add this scrip
48 matches
Mail list logo
