Skip to content

InnoDB restore in the future #97

@dfredell

Description

@dfredell

When a second mysql instance spins up it pulls the snapshot from minio and restores it. During the restore there are a bunch of errors in the logs about "InnoDB: is in the future!"

2017-10-19T13:24:26.436270193Z 2017-10-19 13:24:26 7ffffeda0740 InnoDB: Error: page 330 log sequence number 34726623
2017-10-19T13:24:26.43664837Z InnoDB: is in the future! Current system log sequence number 1633292.
2017-10-19T13:24:26.437019222Z InnoDB: for more information.
2017-10-19T13:24:26.437523598Z InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

I have found that when the primary started up this is in the logs

ERROR manage mysql_tzinfo_to_sql returned error: [Errno 2] No such file or directory

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions