[
https://issues.apache.org/jira/browse/KUDU-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310300#comment-15310300
]
Todd Lipcon commented on KUDU-1475:
-----------------------------------
This looks like a regression of KUDU-140 (probably regressed by
dc72c8b4ace9690e6638e5f19ec98e6a0fc025fd based on my reading of the git log).
It seems that we'd hit this issue if we crash in between preallocating a new
log segment and writing its header. In debug mode, we hit this DCHECK, though
in release mode we probably end with no issue because we correctly handle the
empty log segment as having no entries, and therefore it doesn't matter where
it sorts in the list of segments.
> kudu-tserver restart failed due to log header not initialized.
> --------------------------------------------------------------
>
> Key: KUDU-1475
> URL: https://issues.apache.org/jira/browse/KUDU-1475
> Project: Kudu
> Issue Type: Bug
> Reporter: zhangsong
> Assignee: zhangsong
>
> when restart kudu-tserver , kudu-tserver crash due to fatal check:
> Log file created at: 2016/06/01 12:30:13
> Running on machine: BJHC-Jingo-9492.hadoop.jd.local
> Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
> F0601 12:30:13.938817 13431 log_util.h:208] Check failed:
> header_.IsInitialized()
> kudu-tserver is running in debug mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
