Hi Karthick,
To share a few thoughts on this - I guess a lot depends on your actual
setup / requirements, such as:
- The sort of potential outages you really need to tackle with this
- The volume of data you have to continuously process
- Constraints you may have in terms of messages tha
[
https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327561#comment-15327561
]
Ralph Weires commented on KAFKA-1464:
-
We have similar problems as described by J
[
https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371776#comment-15371776
]
Ralph Weires commented on KAFKA-1464:
-
Thanks a lot for the input - so
[
https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372870#comment-15372870
]
Ralph Weires commented on KAFKA-1464:
-
Another related idea then, since t
Ralph Weires created KAFKA-4946:
---
Summary: Evaluation of kafka_mx4jenable is inverted
Key: KAFKA-4946
URL: https://issues.apache.org/jira/browse/KAFKA-4946
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945156#comment-15945156
]
Ralph Weires commented on KAFKA-3039:
-
Experienced the same problem on v0.10