[
https://issues.apache.org/jira/browse/KUDU-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099094#comment-17099094
]
Balazs Jeszenszky commented on KUDU-3114:
-----------------------------------------
This can be controlled from the application, e.g.:
https://github.com/apache/kudu/blob/branch-1.12.x/src/kudu/util/os-util.cc#L125-L144
, but I'm aware FATAL errors always generate a core if enabled, which is
otherwise preferable. So the request is to turn this into an ERROR instead and
exit cleanly. Best practices on space allocation aside, there is no benefit of
dumping core at this point IMO.
> 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)
