[
https://issues.apache.org/jira/browse/KAFKA-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751715#comment-13751715
]
Jay Kreps commented on KAFKA-1023:
----------------------------------
My recommendation is just to increase the retention. We maintain everything for
7 days. We alert off the consumer lag, but typically these alerts would trigger
if the application falls 20 mins behind we would not wait for 7 days.
> 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
