I would like KAFKA-3296 to be looked at for 0.10, this is causing us
significant issues in our testing. There's a comment in the bug that this is
possibly caused by KAFKA-3215, but that was fixed in 0.9, and KAFKA-3296 is
reproducible in 0.9, so it could be a regression.
SimonC
-Original M
ek or two.
Gwen
On Tue, Mar 22, 2016 at 3:33 AM, Simon Cooper <
simon.coo...@featurespace.co.uk> wrote:
> I would like KAFKA-3296 to be looked at for 0.10, this is causing us
> significant issues in our testing. There's a comment in the bug that
> this is possibly caused
Me:
- Last week:
o DB byte arrays refactor done
o Last week did some work on the zapp performance issues, currently blocked
as cluster is being used
o Also lots of bugfixes around sandbox
- This week:
o Follow up tasks for byte arrays refactor
o Looking at perfor
Simon Cooper would like to recall the message, "Engine team".
Apologies for the random email, sent to the wrong mailing list. Please ignore...
There's been no recent movement on KAFKA-1150. We’re significantly affected by
this bug, trying to achieve small-millisecond transfer latencies on a
replicated system with quite bursty message frequencies.
What are the chances of this bug being fixed in 0.8.2? Could it be marked for
fixing in 0
Hi,
We're planning our work in the next couple of months, and there are several
bugfixes & features in the kafka trunk that we depend on. Can I get an idea on
rough timescales for a 0.8.2 release?
Thanks,
SimonC
Simon Cooper created KAFKA-3837:
---
Summary: Report the name of the blocking thread when throwing
ConcurrentModificationException
Key: KAFKA-3837
URL: https://issues.apache.org/jira/browse/KAFKA-3837
[
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331377#comment-15331377
]
Simon Cooper commented on KAFKA-3837:
-
I would say the thread name is much
[
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331377#comment-15331377
]
Simon Cooper edited comment on KAFKA-3837 at 6/15/16 8:2
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187284#comment-15187284
]
Simon Cooper commented on KAFKA-3296:
-
Are the logs useful?
We've als
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187284#comment-15187284
]
Simon Cooper edited comment on KAFKA-3296 at 3/9/16 4:0
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208201#comment-15208201
]
Simon Cooper commented on KAFKA-3296:
-
{code}Topic:__consumer_off
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210419#comment-15210419
]
Simon Cooper commented on KAFKA-3296:
-
No, these are the only references to Exp
[
https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134158#comment-15134158
]
Simon Cooper commented on KAFKA-2904:
-
We've seen a similar issue when first
[
https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134158#comment-15134158
]
Simon Cooper edited comment on KAFKA-2904 at 2/5/16 1:2
Simon Cooper created KAFKA-3296:
---
Summary: All consumer reads hang indefinately
Key: KAFKA-3296
URL: https://issues.apache.org/jira/browse/KAFKA-3296
Project: Kafka
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Cooper updated KAFKA-3296:
Description:
We've got several integration tests that bring up systems on VMs for testing.
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168952#comment-15168952
]
Simon Cooper commented on KAFKA-3296:
-
We've observed the same behavio
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168952#comment-15168952
]
Simon Cooper edited comment on KAFKA-3296 at 2/26/16 1:0
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169000#comment-15169000
]
Simon Cooper commented on KAFKA-3296:
-
Looks like this breaks for every topic on
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169007#comment-15169007
]
Simon Cooper commented on KAFKA-3296:
-
Example code that breaks that gets the s
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169007#comment-15169007
]
Simon Cooper edited comment on KAFKA-3296 at 2/26/16 1:2
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171739#comment-15171739
]
Simon Cooper commented on KAFKA-3296:
-
This is done right after kafka is installe
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Cooper updated KAFKA-3296:
Attachment: kafkalogs.zip
These are debug logs from the broker when it's in this broken
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173539#comment-15173539
]
Simon Cooper commented on KAFKA-3296:
-
It's definitely a single brok
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Cooper updated KAFKA-3296:
Attachment: controller.zip
Attached debug log kafka controller logs. Also attached the zookeeper
Simon Cooper created KAFKA-1444:
---
Summary: kafka.javaapi.TopicMetadata and PartitionMetadata doesn't
forward the toString method
Key: KAFKA-1444
URL: https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997445#comment-13997445
]
Simon Cooper commented on KAFKA-1182:
-
The current behaviour is causing problems
[
https://issues.apache.org/jira/browse/KAFKA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997719#comment-13997719
]
Simon Cooper commented on KAFKA-1352:
-
Another example is when there's an
[
https://issues.apache.org/jira/browse/KAFKA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071919#comment-14071919
]
Simon Cooper commented on KAFKA-1150:
-
Yes, looks like that patch fixes the i
[
https://issues.apache.org/jira/browse/KAFKA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073025#comment-14073025
]
Simon Cooper commented on KAFKA-1150:
-
Yes, I built a replicated system with
32 matches
Mail list logo
