[
https://issues.apache.org/jira/browse/KUDU-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2182:
------------------------------
Labels: newbie trivial (was: newbie)
> Reenable WAL fsync in the master
> --------------------------------
>
> Key: KUDU-2182
> URL: https://issues.apache.org/jira/browse/KUDU-2182
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.6.0
> Reporter: Adar Dembo
> Priority: Major
> Labels: newbie, trivial
>
> After fixing KUDU-1125, I ran a quick experiment on an internal cluster to
> test the performance impact of enabling log_force_fsync_all in the master. I
> observed that a tablet report with 308 tablet updates took 157 ms. I think
> this is good enough for us to restore the default value to true for Kudu
> masters so that we'll have real metadata durability in the event of a crash.
> I don't know whether we should do this for all master deployments or just for
> single-master ones. Certainly the latter would benefit most, but it might be
> annoying to detect the difference.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
