[
https://issues.apache.org/jira/browse/KUDU-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989064#comment-16989064
]
ASF subversion and git services commented on KUDU-1125:
-------------------------------------------------------
Commit 164d8d20935e4adfb1f99e17ca81b3178d695a2b in kudu's branch
refs/heads/master from Adar Dembo
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=164d8d2 ]
docs: remove log_force_fsync_all known issue
This was fixed in KUDU-1125 (1.6.0) and should have been removed back then.
Change-Id: I9f9ddb9924cdf4f59efeba8fc1bfa1ab6e063df5
Reviewed-on: http://gerrit.cloudera.org:8080/14845
Reviewed-by: Andrew Wong <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <[email protected]>
> 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
> Priority: Major
> 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
(v8.3.4#803005)
