[
https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425338#comment-15425338
]
Todd Lipcon commented on KUDU-38:
---------------------------------
bq. when flushing TabletMetadata, include the lowest live log anchor required
for durability (which is often newer than the oldest log segment being retained
due to time-based or segment-count-based retention)
This is slightly tricky, because during the TabletMetadata::Flush() call,
whichever memory stores were being flushed are actually still alive and
anchored. So, we need to compute the earliest anchored index _not taking into
account those stores currently being flushed_. Otherwise we are "one flush
behind" in our tracking of the anchor.
> bootstrap should not replay logs that are known to be fully flushed
> -------------------------------------------------------------------
>
> Key: KUDU-38
> URL: https://issues.apache.org/jira/browse/KUDU-38
> Project: Kudu
> Issue Type: Improvement
> Components: tablet
> Affects Versions: M3
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> Currently the bootstrap process will process all of the log segments,
> including those that can be trivially determined to contain only durable
> edits. This makes startup unnecessarily slow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
