Recovery Reporter fails when default storage engine is InnoDB and --engine is not InnoDB

[John H. Embretsen]

The Recovery Reporter is incompatible with MySQL Server 5.5 and newer, where the default storage engine is InnoDB instead of MyISAM, in cases where --engine (the RQG option) is not set to be InnoDB.

Recovery fails with STATUS_DATABASE_CORRUPTION because the server could not start on recovery, due to the following fatal error:

    [ERROR] Unknown/unsupported storage engine: InnoDB

The reason is that if --engine=MyISAM (or something else that is not InnoDB) the Recovery Reporter adds "--loose-skip-innodb" to the server's command line options on recovery startup.

Possible solutions:
  1) Remove --loose-skip-innodb from startup options in the Recovery Reporter.
  2) Remove --loose-skip-innodb from startup options in the Recovery Reporter if MySQL version is 5.5 or greater.
  3) Add --default-storage-engine=$engine whenever --engine is not set to InnoDB.

[Philip Stoev (pstoev-askmonty)]

Hello, sorry for the late reply. I think it is best to go for option

1) Remove --loose-skip-innodb from startup options in the Recovery Reporter.

--loose-skip-innodb was meant as a performance optimization to speed up
tests when you are running hundreds of recovery attempts. However, I think
it is OK to sacrifice this optimization as compared to trying to guess which
product and product version is running and what its defaults or capabilities
are.

John, would you like to push this change yourself?

Philip Stoev

----- Original Message -----
From: "John H. Embretsen" <email address hidden>
To: <email address hidden>
Sent: Friday, April 29, 2011 4:14 PM
Subject: [Randgen] [Bug 773237] [NEW] Recovery Reporter fails when
defaultstorage engine is InnoDB and --engine is not InnoDB

> Public bug reported:
>
> The Recovery Reporter is incompatible with MySQL Server 5.5 and newer,
> where the default storage engine is InnoDB instead of MyISAM, in cases
> where --engine (the RQG option) is not set to be InnoDB.
>
> Recovery fails with STATUS_DATABASE_CORRUPTION because the server could
> not start on recovery, due to the following fatal error:
>
> [ERROR] Unknown/unsupported storage engine: InnoDB
>
> The reason is that if --engine=MyISAM (or something else that is not
> InnoDB) the Recovery Reporter adds "--loose-skip-innodb" to the server's
> command line options on recovery startup.
>
> Possible solutions:
> 1) Remove --loose-skip-innodb from startup options in the Recovery
> Reporter.
> 2) Remove --loose-skip-innodb from startup options in the Recovery
> Reporter if MySQL version is 5.5 or greater.
> 3) Add --default-storage-engine=$engine whenever --engine is not set to
> InnoDB.
>
> ** Affects: randgen
> Importance: Undecided
> Assignee: John H. Embretsen (johnemb)
> Status: New
>
> ** Description changed:
>
> The Recovery Reporter is incompatible with MySQL Server 5.5 and newer,
> where the default storage engine is InnoDB instead of MyISAM, in cases
> where --engine (the RQG option) is not set to be InnoDB.
>
> Recovery fails with STATUS_DATABASE_CORRUPTION because the server could
> not start on recovery, due to the following fatal error:
>
> - [ERROR] Unknown/unsupported storage engine: InnoDB
> + [ERROR] Unknown/unsupported storage engine: InnoDB
>
> The reason is that if --engine=MyISAM (or something else that is not
> InnoDB) the Recovery Reporter adds "--loose-skip-innodb" to the server's
> command line options on recovery startup.
>
> Possible solutions:
> - 1) Remove --lose-skip-innodb from startup options in the Recovery
> Reporter.
> - 2) Remove --loose-skip-innodb from startup options in the Recovery
> Reporter if MySQL version is 5.5 or greater.
> - 3) Add --default-storage-engine=$engine whenever --engine is not set
> to InnoDB.
> + 1) Remove --loose-skip-innodb from startup options in the Recovery
> Reporter.
> + 2) Remove --loose-skip-innodb from startup options in the Recovery
> Reporter if MySQL version is 5.5 or greater.
> + 3) Add --default-storage-engine=$engine whenever --engine is not set to
> InnoDB.
>
> ** Changed in: randgen
> Assignee: (unassigned) ...

[Anitha Gopi (anitha-gopi)]

This is an auto-replied message. I am on vacation from May 2nd to May 6th. I will reply to your e mail after I return

[Anitha Gopi (anitha-gopi)]

This is an auto-replied message. I am on vacation from May 2nd to May 6th. I will reply to your e mail after I return

[John H. Embretsen (johnemb)]

Philip, thanks for the comment. I am OK with going for option 1) too. I can do the change myself.

[John H. Embretsen (johnemb)]

Should be fixed in lp:randgen revid <email address hidden>:

revno: 742
committer: John H. Embretsen <email address hidden>
branch nick: randgen-testrun
timestamp: Fri 2011-05-13 16:36:26 +0200
message:
  Fix for Bug#773237 (on Launchpad): Recovery Reporter fails when default storage engine is InnoDB and --engine is not InnoDB
  The fix implements solution option 1), i.e. it removes --loose-skip-innodb from startup options in the Recovery Reporter.
  The downside is that recovery time may increase, the upside is that the Recovery reporter works also when InnoDB is the default storage engine.