[
https://issues.apache.org/jira/browse/KUDU-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099242#comment-17099242
]
Alexey Serbin commented on KUDU-3114:
-------------------------------------
Right, it's possible to disable coredumps for Kudu processes by adding
{{\-\-disable_core_dumps}} even if the limit for core files size of set to
non-zero. My point was that enabling/disabling coredumps per {{LOG(FATAL)}}
instance is not feasible.
Dumping a core file might have sense when troubleshooting an issue: e.g., if
there is a bug in computing the number of bytes to allocate, what event
triggered the issue if it's requested to allocate unexpectedly high amount of
space, etc. Probably, we can keep that for DEBUG builds only.
I'm OK with keeping this JIRA item open (so, I'm re-opening it). Feel free to
submit a patch to address the issue as needed.
> tserver writes core dump when reporting 'out of space'
> ------------------------------------------------------
>
> Key: KUDU-3114
> URL: https://issues.apache.org/jira/browse/KUDU-3114
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.7.1
> Reporter: Balazs Jeszenszky
> Priority: Major
> Fix For: n/a
>
>
> Fatal log has:
> {code}
> F0503 23:56:27.359544 40012 status_callback.cc:35] Enqueued commit operation
> failed to write to WAL: IO error: Insufficient disk space to allocate 8388608
> bytes under path <PATH> (39973171200 bytes available vs 39988335247 bytes
> reserved) (error 28)
> {code}
> Generating a core file in this case yields no benefit, and potentially
> compounds the problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
