[
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331377#comment-15331377
]
Simon Cooper edited comment on KAFKA-3837 at 6/15/16 8:23 AM:
--
I would say
[
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331377#comment-15331377
]
Simon Cooper commented on KAFKA-3837:
-
I would say the thread name is much more useful
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
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 by KAFKA-3215, but that w
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210419#comment-15210419
]
Simon Cooper commented on KAFKA-3296:
-
No, these are the only references to Expired in the logs
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208201#comment-15208201
]
Simon Cooper commented on KAFKA-3296:
-
{code}Topic:__consumer_offsetsPartitionCount:50
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
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187284#comment-15187284
]
Simon Cooper edited comment on KAFKA-3296 at 3/9/16 4:07 PM:
-
Are the logs
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187284#comment-15187284
]
Simon Cooper commented on KAFKA-3296:
-
Are the logs useful?
We've also started seeing a (possibly
[
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
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173539#comment-15173539
]
Simon Cooper commented on KAFKA-3296:
-
It's definitely a single broker, and a standard single-node
[
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 state
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171739#comment-15171739
]
Simon Cooper commented on KAFKA-3296:
-
This is done right after kafka is installed on the VM - we
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169007#comment-15169007
]
Simon Cooper edited comment on KAFKA-3296 at 2/26/16 1:26 PM:
--
Example code
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169007#comment-15169007
]
Simon Cooper commented on KAFKA-3296:
-
Example code that breaks that gets the start and end offset
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169000#comment-15169000
]
Simon Cooper commented on KAFKA-3296:
-
Looks like this breaks for every topic on the broker (only
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168952#comment-15168952
]
Simon Cooper edited comment on KAFKA-3296 at 2/26/16 1:07 PM:
--
We've observed
[
https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168952#comment-15168952
]
Simon Cooper commented on KAFKA-3296:
-
We've observed the same behaviour with a 0.9.0.0 consumer
[
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.
We've
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
Apologies for the random email, sent to the wrong mailing list. Please ignore...
Simon Cooper would like to recall the message, "Engine team".
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
[
https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134158#comment-15134158
]
Simon Cooper commented on KAFKA-2904:
-
We've seen a similar issue when first starting up brokers
[
https://issues.apache.org/jira/browse/KAFKA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134158#comment-15134158
]
Simon Cooper edited comment on KAFKA-2904 at 2/5/16 1:24 PM:
-
We've seen
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
[
https://issues.apache.org/jira/browse/KAFKA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073025#comment-14073025
]
Simon Cooper commented on KAFKA-1150:
-
Yes, I built a replicated system
[
https://issues.apache.org/jira/browse/KAFKA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071919#comment-14071919
]
Simon Cooper commented on KAFKA-1150:
-
Yes, looks like that patch fixes the issue
[
https://issues.apache.org/jira/browse/KAFKA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997719#comment-13997719
]
Simon Cooper commented on KAFKA-1352:
-
Another example is when there's an exception
[
https://issues.apache.org/jira/browse/KAFKA-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997445#comment-13997445
]
Simon Cooper commented on KAFKA-1182:
-
The current behaviour is causing problems
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-1444
31 matches
Mail list logo