[
https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281106#comment-15281106
]
Todd Lipcon commented on KUDU-38:
---------------------------------
Just pushed some patches to gerrit with some low hanging fruit here:
http://gerrit.cloudera.org:8080/#/c/3037/ is the big one. On a cluster where
each node has a few TB of data (349 replicas) the bootstrap time went down from
288 seconds to 106 seconds with these patches. It could still be much better,
though, by doing something like what this JIRA is discussing.
> 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)
