[
https://issues.apache.org/jira/browse/KUDU-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1949.
-------------------------------
Resolution: Fixed
Assignee: Todd Lipcon
Fix Version/s: 1.4.0
Committed in da2055f64d9ed717be6a3ca62868964aa54dc57d
> MM should trigger flushes before memory backpressure kicks in
> -------------------------------------------------------------
>
> Key: KUDU-1949
> URL: https://issues.apache.org/jira/browse/KUDU-1949
> Project: Kudu
> Issue Type: Bug
> Components: perf, tserver
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 1.4.0
>
>
> Based on some analysis in
> https://docs.google.com/document/d/1U1IXS1XD2erZyq8_qG81A1gZaCeHcq2i0unea_eEf5c/edit#heading=h.b98m0h4dgd3w
> it seems like a major cause of slowness and potential timeouts is that we
> start issuing memory-pressure rejections at the same limit at which we decide
> to start flushing data. Given that flushes take some amount of time, and
> given that they may need to wait for compactions to finish before they get
> scheduled, we cause a lot of rejections even if we could otherwise keep up
> with the flush rate.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
