You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dinesh Bhat (JIRA)" <ji...@apache.org> on 2016/10/19 23:52:58 UTC

[jira] [Commented] (KUDU-1573) In corner cases , tablet could not recovery successfully from node crash.

    [ https://issues.apache.org/jira/browse/KUDU-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15590278#comment-15590278 ] 

Dinesh Bhat commented on KUDU-1573:
-----------------------------------

[~bruceSz] we pre-allocate the log segments for performance reasons, which means fallocate() would have zero'ed them out. 

> 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)