[
https://issues.apache.org/jira/browse/KUDU-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099075#comment-17099075
]
Alexey Serbin commented on KUDU-3114:
-------------------------------------
Thank you for reporting the issue.
The way how fatal inconsistencies are handled in Kudu doesn't provide control
to choose between coredump behavior. The behavior of it's controlled at
different level: the environment that Kudu processes are run with (check
{{ulimit -c}}).
As a good operational practice, it's advised to separate the location for core
files (some directory at system partition/volume?) and the directories where
Kudu stores its data and WAL. Also, consider [enabling mini-dumps in
Kudu|https://kudu.apache.org/docs/troubleshooting.html#crash_reporting] and
disabling core files if dumping cores isn't feasible due to space limitations.
> 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
>
> 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)
