[
https://issues.apache.org/jira/browse/KUDU-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wong resolved KUDU-2356.
-------------------------------
Fix Version/s: 1.12.0
Assignee: Andrew Wong
Resolution: Fixed
Re-merged as a85c3302abf935457e4d0f9d5326f0b612e0b614. Watched over the flaky
test dashboard and haven't seen anything surprising and WAL related in the past
few days.
I put this on a tserver and the post-bootstrap memory usage went from 9.08GB to
5.55GB with the patch.
> Idle WALs can consume significant memory
> ----------------------------------------
>
> Key: KUDU-2356
> URL: https://issues.apache.org/jira/browse/KUDU-2356
> Project: Kudu
> Issue Type: Improvement
> Components: log, tserver
> Affects Versions: 1.7.0
> Reporter: Todd Lipcon
> Assignee: Andrew Wong
> Priority: Major
> Fix For: 1.12.0
>
> Attachments: heap.svg
>
>
> I grabbed a heap sample of a tserver which has been running a write workload
> for a little while and found that 750MB of memory is used by faststring
> allocations inside WritableLogSegment::WriteEntryBatch. It seems like this is
> the 'compress_buf_' member. This buffer always resizes up during a log write
> but never shrinks back down, even when the WAL is idle. We should consider
> clearing the buffer after each append, or perhaps after a short timeout like
> 100ms after a WAL becomes idle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
