[
https://issues.apache.org/jira/browse/KUDU-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated KUDU-2134:
--------------------------
Code Review: https://gerrit.cloudera.org/#/c/7966/
> Defer block transaction commit to the end of a tablet copy
> ----------------------------------------------------------
>
> Key: KUDU-2134
> URL: https://issues.apache.org/jira/browse/KUDU-2134
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.5.0
> Reporter: Adar Dembo
> Assignee: Hao Hao
> Fix For: 1.6.0
>
>
> While looking at KUDU-2131, it occurred to me that we could solve the
> "batched fsyncs could lead to a tablet copy session timeout" problem entirely
> if we simply deferred the commit of the blocks until after we're done with
> the session. That would mean deferring it until after {{DownloadWALs}}.
> That's probably a good thing to do anyway:
> # If {{DownloadWALs}} fails there's no reason to pay the fsync price and
> commit all those blocks.
> # While {{DownloadWALs}} is running the kernel has more time to eagerly flush
> the blocks, so the fsyncs at the end could be cheaper.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
