[
https://issues.apache.org/jira/browse/KUDU-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457444#comment-15457444
]
zhangsong edited comment on KUDU-1573 at 9/2/16 4:06 AM:
---------------------------------------------------------
Great~
So the root cause of this issue is after creating log segment, power outrage/
kernel panic(in my case , it is RAID card failure ) before OS has sync data
into the disk successfully and left those log segment had \0 data? Wonder where
the \0 data come from.
was (Author: brucesz):
Great~
So the root cause of this issue is after creating log segment, power outrage/
kernel panic() before OS has sync data into the disk successfully and left
those log segment had \0 data? Wonder where the \0 data come from.
> In corner cases , tablet could not recovery successfully from node crash.
> ---------------------------------------------------------------------------
>
> Key: KUDU-1573
> URL: https://issues.apache.org/jira/browse/KUDU-1573
> Project: Kudu
> Issue Type: Bug
> Reporter: zhangsong
> Attachments: wal_recovery_dir.zip
>
>
> Last friday ,one of nodes of my kudu cluster crashed and , tablet can not
> recovery successfully after restart kudu-tserver, i observed error messages
> from log:
> (TABLET_DATA_READY): Corruption: Could not open LogReader. Reason: Unable to
> initialize log reader: Segment sequence numbers are not consecutive. Previous
> segment: seqno 0, path
> /export/servers/kudu/tserver_wal_data_7052/wals/ed0d8b3a835e4c27afe695252ad0b8f5.recovery/wal-000000018;
> Current segment: seqno 17, path
> /export/servers/kudu/tserver_wal_data_7052/wals/ed0d8b3a835e4c27afe695252ad0b8f5.recovery/wal-000000017
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
