[
https://issues.apache.org/jira/browse/KUDU-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-761.
------------------------------
Fix Version/s: NA
Resolution: Duplicate
> TS seg fault after short log append
> -----------------------------------
>
> Key: KUDU-761
> URL: https://issues.apache.org/jira/browse/KUDU-761
> Project: Kudu
> Issue Type: Bug
> Components: log
> Affects Versions: M5
> Reporter: Adar Dembo
> Priority: Major
> Fix For: NA
>
>
> I was running tpch_real_world with SF=6000 on a2414. Towards the end of the
> run, flush MM ops consistently won out over log gc MM due to memory pressure.
> Eventually we ran out of disk space on the disk hosting the logs:
> {noformat}
> E0511 05:45:47.913038 8174 log.cc:130] Error appending to the log: IO error:
> pwritev error: expected to write 254370 bytes, wrote 145525 bytes instead
> {noformat}
> What followed was a SIGSEGV:
> {noformat}
> PC: @ 0x0
> *** SIGSEGV (@0x0) received by PID 8004 (TID 0x7fae308fd700) from PID 0;
> stack trace: ***
> @ 0x3d4ae0f500
> @ 0x0
> @ 0x8a2791 kudu::log::LogEntryPB::~LogEntryPB()
> @ 0x8a2272 kudu::log::LogEntryBatchPB::~LogEntryBatchPB()
> @ 0x8a22e1 kudu::log::LogEntryBatchPB::~LogEntryBatchPB()
> @ 0x892de4 kudu::log::Log::AppendThread::RunThread()
> {noformat}
> There's not much we can do when we run out of disk space, but better to crash
> with a CHECK or something than to SIGSEGV.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
