[jira] [Resolved] (KUDU-1125) Reduce impact of enabling fsync on the master

["Adar Dembo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo resolved KUDU-1125.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Commit 29a7568ddb5d24b1faf583b45d38884bfeb2b260 changed the catalog manager to batch up all tablet updates in a given tablet report.

We could still downgrade some persistent state to in-memory state (e.g. tablet leader uuids?) to reduce update frequency even further, but with this improvement and with Todd's earlier commit 3b6ab64497bb091d0a94d6085c4fbd68da5cecda (don't rewrite tablet state if it hasn't actually changed), the performance is already quite good for our current scale targets, so I'm marking this JIRA as fixed.

> Reduce impact of enabling fsync on the master
> ---------------------------------------------
>
>                 Key: KUDU-1125
>                 URL: https://issues.apache.org/jira/browse/KUDU-1125
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: master
>    Affects Versions: Feature Complete
>            Reporter: Jean-Daniel Cryans
>            Assignee: Adar Dembo
>              Labels: data-scalability
>             Fix For: 1.6.0
>
>
> First time running ITBLL since we enabled fsync in the master and I'm now seeing RPCs timing out because the master is always ERROR_SERVER_TOO_BUSY. In the log I can see a lot of elections going on and the queue is always full.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)