Misleading innodb_extra_rsegments documentation

Bug #997469 reported by Laurynas Biveinis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Undecided
Hrvoje Matijakovic
5.1
Fix Released
Undecided
Hrvoje Matijakovic

Bug Description

Original report by Simon Kuhn, verified by me:

According to the Percona docs, innodb_extra_rsegments can be changed simply by restarting MySQL (with innodb_fast_shutdown disabled). However, I'm not able to get this to actually take effect (as shown by information_schema.innodb_rseg).

With Percona Server 5.1.58-rel12.9 (and also 5.1.62-rel13.2), I've done the following:

- Modify /etc/mysql/my.conf:
   [mysqld]
   innodb_extra_rsegments = 20

mysql> set global innodb_fast_shutdown=0; \q

/etc/init.d/mysql restart

mysql> show global variables like 'innodb_extra_rsegments';
+------------------------+-------+
| Variable_name | Value |
+------------------------+-------+
| innodb_extra_rsegments | 20 |
+------------------------+-------+
1 row in set (0.00 sec)

mysql> SELECT COUNT(*) FROM information_schema.innodb_rseg;
+----------+
| COUNT(*) |
+----------+
| 1 |
+----------+
1 row in set (0.00 sec)

Related branches

Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

That is expected behavior. The documentation is wrong.
For 5.1 you need to create database from zero to have innodb_extra_rsegments working.

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

In that case we have to fix the docs, assigning to Hrvoje.

Changed in percona-server:
assignee: nobody → Hrvoje Matijakovic (hrvojem)
summary: - innodb_extra_rsegments apparently ignored
+ Misleading innodb_extra_rsegments documentation
Changed in percona-server:
status: Confirmed → In Progress
Changed in percona-server:
status: In Progress → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2752

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.