innodb.file-per-table not a recognized option for drizzled.cnf

Bug #657010 reported by m00dawg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Confirmed
High
Monty Taylor
7.0
Confirmed
High
Monty Taylor

Bug Description

Using any of the following combinations to enable to enable InnoDB file per table does not seem to work:

innodb.file-per-table
innodb.file-per-table = 1

[innodb]
file-per-table
file-per-table = 1

For example:

root@mcp:~# cat /etc/drizzle/drizzled.cnf
datadir = /var/lib/drizzle
pid-file = /var/lib/drizzle/mcp.pid

[innodb]
buffer-pool-size = 5M
flush-log-at-trx-commit = 0
file-format = Barracuda
file-per-table = 1

[mysql-protocol]
port = 3307
bind-address = 127.0.0.1
root@mcp:~# /etc/init.d/drizzle-server start
 * Starting Drizzle database server drizzled
/usr/sbin/drizzled: extra parameter in 'innodb.file-per-table'.
Use --help to get a list of available options
Aborting
/usr/sbin/drizzled: extra parameter in 'innodb.file-per-table'.
Use --help to get a list of available options
Aborting
   ...done.
root@mcp:~# drizzle
ERROR:
drizzle_state_connect:could not connect
root@mcp:~#

Similar example:

root@mcp:~# cat /etc/drizzle/drizzled.cnf
datadir = /var/lib/drizzle
pid-file = /var/lib/drizzle/mcp.pid

[innodb]
buffer-pool-size = 5M
flush-log-at-trx-commit = 0
file-format = Barracuda
file-per-table

[mysql-protocol]
port = 3307
bind-address = 127.0.0.1
root@mcp:~# /etc/init.d/drizzle-server start
 * Starting Drizzle database server drizzled
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<drizzled::program_options::invalid_syntax> >'
  what(): unrecognized line in 'file-per-table'
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<drizzled::program_options::invalid_syntax> >'
  what(): unrecognized line in 'file-per-table'
   ...done.

However, invoking it on the command-line does work as long as the configuration file options are removed:

root@mcp:~# cat /etc/drizzle/drizzled.cnf
datadir = /var/lib/drizzle
pid-file = /var/lib/drizzle/mcp.pid

[innodb]
buffer-pool-size = 5M
flush-log-at-trx-commit = 0
file-format = Barracuda
#file-per-table = 1

[mysql-protocol]
port = 3307
bind-address = 127.0.0.1
root@mcp:~# drizzled --innodb.file-per-table
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins.
101008 18:08:28 InnoDB: highest supported file format is Barracuda.
101008 18:08:28 InnoDB Plugin 1.0.4 started; log sequence number 44274
Listening on 0.0.0.0:4427
Listening on :::4427
Listening on 127.0.0.1:3307
drizzled: ready for connections.
Version: '2010.09.1802' Source distribution (drizzle)
...

The other InnoDB options I have tried do seem to work, although I have not gone through an exhaustive test of all InnoDB configuration options.

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

innodb.file-per-table = true works in current trunk, = 1 does not.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.