[
https://issues.apache.org/jira/browse/KUDU-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310031#comment-15310031
]
zhangsong commented on KUDU-1475:
---------------------------------
core dump provide little info , bt returns this :
Failed to read a valid object file image from memory.
Core was generated by `/export/servers/kudu/release/kudu-tserver
-fs_wal_dir=/export/servers/kudu/tser'.
Program terminated with signal SIGABRT, Aborted.
#0 0x0000003296632925 in ?? ()
[Current thread is 1 (LWP 3961)]
content in kudu-tserver.INFO right before the dcheck is :
I0601 17:32:22.098095 3948 log_util.cc:569] Scanning
/export/servers/kudu/tserver_wal_data_7052/wals/4dad4d39d8fc4d8d9d1c8392270da48d.recovery/wal-000000080
for valid entry headers following offset 29790817...
I0601 17:32:22.103221 4080 tablet_service.cc:646] Processing DeleteTablet for
tablet 1e5f529a8e284305a97ce3e1c1a2b99c with delete_type TABLET_DATA_DELETED
(Table deleted at 2016-06-01 14:00:54 CST) from {real_user=ldbadmin, eff_user=}
at 172.22.86.16:14048
I0601 17:32:22.105959 4080 tablet_service.cc:646] Processing DeleteTablet for
tablet d160f6bf09ba43bea3bd8fe6ae89dfc7 with delete_type TABLET_DATA_DELETED
(Table deleted at 2016-06-01 15:42:09 CST) from {real_user=ldbadmin, eff_user=}
at 172.22.86.16:14048
I0601 17:32:22.189025 3961 log_util.cc:569] Scanning
/export/servers/kudu/tserver_wal_data_7052/wals/967aa7c3bce64e8ebb1c378ef482d225.recovery/wal-000000060
for valid entry headers following offset 43340777...
I0601 17:32:22.242414 3961 log_util.cc:606] Found no log entry headers
I0601 17:32:22.242482 3961 log_util.cc:215] Ignoring log segment corruption in
/export/servers/kudu/tserver_wal_data_7052/wals/967aa7c3bce64e8ebb1c378ef482d225.recovery/wal-000000060
because there are no log entries following the corrupted one. The server
probably crashed in the middle of writing an entry to the write-ahead log or
downloaded an active log via remote bootstrap. Error detail: Corruption: CRC
mismatch in log entry header: Log file corruption detected. Failed trying to
read batch #0 at offset 43340765 for log segment
/export/servers/kudu/tserver_wal_data_7052/wals/967aa7c3bce64e8ebb1c378ef482d225.recovery/wal-000000060:
Prior entries: [off=42660959 REPLICATE (1.5990)] [off=42667135 COMMIT
(1.5990)] [off=43334589 REPLICATE (1.5991)] [off=43340765 COMMIT (1.5991)]
I0601 17:32:22.242563 3961 log_util.cc:359] Successfully rebuilt footer for
segment:
/export/servers/kudu/tserver_wal_data_7052/wals/967aa7c3bce64e8ebb1c378ef482d225.recovery/wal-000000060
(valid entries through byte offset 43340765)
F0601 17:32:22.243938 3961 log_util.h:208] Check failed:
header_.IsInitialized()
> 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)
