Vadim,

I think this is valid bug. Users upgrading MySQL 5.1 with Innodb plugin may
have such lines in my.cnf
and can get crashes.

If Percona Server does not support these options we need error message in
error log and failing to start
but not crash.

On Mon, Jan 17, 2011 at 3:43 PM, Vadim Tkachenko <email address hidden> wrote:

> options
> ignore-builtin-innodb
>  plugin-load=innodb=ha_innodb.so
>
> are not supported in Percona Server and may give unpredictable result.
>
> Percona Server comes with XtraDB ( advanced InnoDB-plugin by default).
>
>
> ** Changed in: percona-server
>       Status: New => Invalid
>
> --
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
> https://bugs.launchpad.net/bugs/704216
>
> Title:
>  Creation of compressed innodb table fails
>
> Status in Percona Server with XtraDB:
>   Invalid
>
> Bug description:
>  OS: Ubuntu 10.04 x86_64
>  Percona Server: 5.1.54-rel12.5 (Rev. 188)
>
>  Default options were altered with:
>  ignore-builtin-innodb
>  plugin-load=innodb=ha_innodb.so
>  innodb_file_per_table
>
>  While issuing SQL statement to create compressed InnoDB table mysql
>  client throws the following error:
>
>  mysql> create table t1 (a varchar(20)) ENGINE=InnoDB ROW_FORMAT=COMPRESSED
> KEY_BLOCK_SIZE=4;
>  ERROR 2006 (HY000): MySQL server has gone away
>  No connection. Trying to reconnect...
>  Connection id:    1
>  Current database: test
>
>  ERROR 2006 (HY000): MySQL server has gone away
>  No connection. Trying to reconnect...
>  ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (111)
>  ERROR:
>  Can't connect to the server
>
>  mysql>
>
>  After specified statement mysql client is n more operable, after
>  restarting mysql client (not the server) - it keeps working.
>
>  Please find relevant log entries from daemon logger below:
>
>  Jan 18 02:30:31 dev302 mysqld: Version: '5.1.54-rel12.5'  socket:
> '/var/run/mysqld/mysqld.sock'  port: 3306  (Percona Server (GPL), 12.5 ,
> Revision 188)
>  Jan 18 02:30:39 dev302 mysqld: 110118  2:30:39 - mysqld got signal 11 ;
>  Jan 18 02:30:39 dev302 mysqld: This could be because you hit a bug. It is
> also possible that this binary
>  Jan 18 02:30:39 dev302 mysqld: or one of the libraries it was linked
> against is corrupt, improperly built,
>  Jan 18 02:30:39 dev302 mysqld: or misconfigured. This error can also be
> caused by malfunctioning hardware.
>  Jan 18 02:30:39 dev302 mysqld: We will try our best to scrape up some info
> that will hopefully help diagnose
>  Jan 18 02:30:39 dev302 mysqld: the problem, but since we have already
> crashed, something is definitely wrong
>  Jan 18 02:30:39 dev302 mysqld: and this may fail.
>  Jan 18 02:30:39 dev302 mysqld:
>  Jan 18 02:30:39 dev302 mysqld: key_buffer_size=16777216
>  Jan 18 02:30:39 dev302 mysqld: read_buffer_size=131072
>  Jan 18 02:30:39 dev302 mysqld: max_used_connections=1
>  Jan 18 02:30:39 dev302 mysqld: max_threads=151
>  Jan 18 02:30:39 dev302 mysqld: threads_connected=1
>  Jan 18 02:30:39 dev302 mysqld: It is possible that mysqld could use up to
>  Jan 18 02:30:39 dev302 mysqld: key_buffer_size + (read_buffer_size +
> sort_buffer_size)*max_threads = 346599 K
>  Jan 18 02:30:39 dev302 mysqld: bytes of memory
>  Jan 18 02:30:39 dev302 mysqld: Hope that's ok; if not, decrease some
> variables in the equation.
>  Jan 18 02:30:39 dev302 mysqld:
>
>  strace outputs are attached in tar archive. mysqld pid is 972
>
>
>


-- 
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501   Skype:  peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Join us for Percona Live Event, San Francisco, Feb 16
http://www.percona.com/events/percona-live-san-francisco-2011/