[
https://issues.apache.org/jira/browse/KUDU-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-1727.
------------------------------
Resolution: Fixed
Assignee: Hao Hao
Fix Version/s: 1.5.0
Fixed in commit 59ca360.
> Add Log Block Manager support for multiple un-synced blocks in a container
> --------------------------------------------------------------------------
>
> Key: KUDU-1727
> URL: https://issues.apache.org/jira/browse/KUDU-1727
> Project: Kudu
> Issue Type: Improvement
> Components: tablet
> Reporter: Mike Percy
> Assignee: Hao Hao
> Fix For: 1.5.0
>
>
> Per [~adar], the Log Block Manager treats new blocks as either being open
> (and thus not fsync'ed) or closed (and thus fsync'ed), but an open block is
> also considered to be in progress, thus preventing its container from being
> used for other new blocks.
> If we want to support bulk fsync after many tablet operations, such as what
> we would like to do in Tablet Copy, then we need to take this apart;
> otherwise deferring fsyncs for 1000 blocks means 1000 open containers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
