Neha Narkhede 2013-08-25, 03:33
Jay Kreps 2013-08-25, 20:23
[ https://issues.apache.org/jira/browse/KAFKA-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751705#comment-13751705 ]
Micah Whitacre commented on KAFKA-1023:
Thanks for the feedback. The fact that LogManager was sealed helped to indicate this was not a common integration point. The concern of losing a message due to a consumer being slow or down for a period and the log manager removing messages due to space was what initially inspired looking at it through this approach.
Is there by chance a way of alarming/tracking if a log roll is about to occur and not all consumers have an offset higher than the values to be deleted?
> Allow Injectable LogManager
> Key: KAFKA-1023
> URL: https://issues.apache.org/jira/browse/KAFKA-1023
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Micah Whitacre
> Currently the LogManager is responsible for deleting and cleaning up messages based on time or size. It'd be nice to be able enhance the LogManager to not only perform the cleanup but maybe also backup the messages eligible for deletion to a custom location (hdfs). This would allow a backup plan in the case of a consumer not able to keep up with the messages and data being lost due to log rolling.
> Currently LogManager is sealed so no one can extend it but additionally we'd need a way to inject the custom LogManager into the KafkaServer.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Jay Kreps 2013-08-27, 21:01