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) => John H. Embretsen (johnemb)
>
> -- 
> You received this bug notification because you are a member of Random
> Query Generator Team, which is subscribed to Random Query Generator.
> https://bugs.launchpad.net/bugs/773237
>
> Title:
>  Recovery Reporter fails when default storage engine is InnoDB and
>  --engine is not InnoDB
>
> Status in SQL Generator for testing SQL servers (MySQL, JavaDB, 
> PostgreSQL):
>  New
>
> Bug description:
>  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.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~randgen
> Post to     : <email address hidden>
> Unsubscribe : https://launchpad.net/~randgen
> More help   : https://help.launchpad.net/ListHelp
>