You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/03/15 22:18:41 UTC

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

    [ https://issues.apache.org/jira/browse/KUDU-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927086#comment-15927086 ] 

Todd Lipcon commented on KUDU-1125:
-----------------------------------

Another effect of the per-tablet SyncWrite call is that the initial report for a tablet server with a lot of tablets generates a _lot_ if individual transactions, and is liable to time out. It also generates a _huge_ trace message.

> Reduce impact of enabling fsync on the master
> ---------------------------------------------
>
>                 Key: KUDU-1125
>                 URL: https://issues.apache.org/jira/browse/KUDU-1125
>             Project: Kudu
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: Feature Complete
>            Reporter: Jean-Daniel Cryans
>
> 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.3.15#6346)