[
https://issues.apache.org/jira/browse/KUDU-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626899#comment-15626899
]
Todd Lipcon commented on KUDU-1551:
-----------------------------------
I think in this case we shouldn't continue reading the segment at all after we
hit the path that sees that there is no log header. In other words, we should
delete the segment and ignore it, instead of trying to continue with the
'rewind schema' code path.
> kudu-tserver can not start up after experience node crash
> ---------------------------------------------------------
>
> Key: KUDU-1551
> URL: https://issues.apache.org/jira/browse/KUDU-1551
> Project: Kudu
> Issue Type: Bug
> Components: log
> Affects Versions: 1.0.1
> Reporter: zhangsong
> Priority: Critical
> Labels: newbie
>
> after experience node crash ,kudu-tserver can not restarted successfully,
> Fatal log :
> "I0804 18:36:04.109537 1909 log_util.cc:359] Successfully rebuilt footer for
> segment:
> /export/servers/kudu/tserver_wal_data_7052/wals/2c329cd1b4bf4850b9b9e2e0613f73d9.recovery/wal-000000001
> (valid entries through byte offset 1993)
> I0804 18:36:04.109566 1909 tablet.cc:854] T 2c329cd1b4bf4850b9b9e2e0613f73d9
> Rewinding schema during bootstrap to Schema [
>
> ]
> F0804 18:36:04.109634 1909 memrowset.cc:102] Check failed:
> schema.has_column_ids()"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
