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

zhangsong commented on KUDU-1551:
---------------------------------

[~tlipcon] for the workaround , in below code , pit_schema will be empty (has 
no column id), if segments[0] is preallocated with no header written.
So what i need to do is delete this segment? Should i continue to rewind 
pit_schema from segments[1]?
 if (!segments.empty()) {
    const scoped_refptr<ReadableLogSegment>& segment = segments[0];
    // Set the point-in-time schema for the tablet based on the log header.
    Schema pit_schema;
    RETURN_NOT_OK_PREPEND(SchemaFromPB(segment->header().schema(), &pit_schema),
                          "Couldn't decode log segment schema");
    RETURN_NOT_OK_PREPEND(tablet_->RewindSchemaForBootstrap(
                              pit_schema, segment->header().schema_version()),
                          "couldn't set point-in-time schema");
  }

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

Reply via email to