[
https://issues.apache.org/jira/browse/KUDU-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo reassigned KUDU-1931:
--------------------------------
Assignee: Adar Dembo
Forgot to mention: it's after a flush or compact operation that a server will
reopen the new blocks and account for their memory footprint, hence triggering
the crash.
> Servers using the FBM may crash after a Flush
> ---------------------------------------------
>
> Key: KUDU-1931
> URL: https://issues.apache.org/jira/browse/KUDU-1931
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: 1.2.0
> Reporter: Adar Dembo
> Assignee: Adar Dembo
> Fix For: 1.4.0
>
>
> The file block manager interacts with RandomAccessFiles via the file cache,
> and the file cache RandomAccessFile descriptor's implementation of
> memory_footprint() can lead to a crash, due to its use of std::make_shared()
> to allocate the underlying memory.
> Just how likely the crash is to occur is unclear: it happens with near
> certainty using glibc's malloc, but I haven't seen it happen with tcmalloc.
> Because of that, I'm inclined to restrict the fix to 1.4 rather than get it
> into 1.3 (or even 1.2.1).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
