2013-12-12 11:08:18 |
Przemek |
bug |
|
|
added bug |
2013-12-12 11:09:54 |
Przemek |
description |
In:
http://www.percona.com/doc/percona-server/5.5/scalability/innodb_extra_rseg.html#INNODB_RSEG
There is example innodb_extra_rsegments variable, which exists only in PS 5.1. Since MySQL/PS 5.5 there is a new variable:
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_rollback_segments
However, it can only limit the number of rollback segments used within a transaction, but it cannot limit physically available segments (128).
mysql [localhost] {msandbox} ((none)) > select @@version;
+----------------+
| @@version |
+----------------+
| 5.5.34-rel32.0 |
+----------------+
mysql [localhost] {msandbox} ((none)) > select count(*) from information_schema.innodb_rseg;
+----------+
| count(*) |
+----------+
| 128 |
+----------+
For Percona Server 5.6, the documentation:
http://www.percona.com/doc/percona-server/5.6/diagnostics/misc_info_schema_tables.html
also has this wrong example with innodb_extra_rsegments variable.
Also, in 5.6 case, it is possible to initialize innodb system tablespace with lower number of rollback segments by using one of these variables before InnoDB table space is created:
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_rollback_segments
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_logs
But then, if Innodb_available_undo_logs is lower then 128, querying the information_schema.XTRADB_RSEG leads to server crash, see #1260259.
And the example select in http://www.percona.com/doc/percona-server/5.6/diagnostics/misc_info_schema_tables.html#XTRADB_RSEG shows information_schema.innodb_rseg instead of information_schema.xtradb_rseg. |
In:
http://www.percona.com/doc/percona-server/5.5/scalability/innodb_extra_rseg.html#INNODB_RSEG
There is example innodb_extra_rsegments variable, which exists only in PS 5.1. Since MySQL/PS 5.5 there is a new variable:
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_rollback_segments
However, it can only limit the number of rollback segments used within a transaction, but it cannot limit physically available segments (128).
mysql [localhost] {msandbox} ((none)) > select @@version;
+----------------+
| @@version |
+----------------+
| 5.5.34-rel32.0 |
+----------------+
mysql [localhost] {msandbox} ((none)) > select count(*) from information_schema.innodb_rseg;
+----------+
| count(*) |
+----------+
| 128 |
+----------+
For Percona Server 5.6, the documentation:
http://www.percona.com/doc/percona-server/5.6/diagnostics/misc_info_schema_tables.html
also has this wrong example with innodb_extra_rsegments variable.
Also, in 5.6 case, it is possible to initialize innodb system tablespace with lower number of rollback segments by using one of these variables before InnoDB table space is created:
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_rollback_segments
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_logs
But then, if Innodb_available_undo_logs is lower then 128, querying the information_schema.XTRADB_RSEG leads to server crash, see lp:1260259.
And the example select in http://www.percona.com/doc/percona-server/5.6/diagnostics/misc_info_schema_tables.html#XTRADB_RSEG shows information_schema.innodb_rseg instead of information_schema.xtradb_rseg. |
|
2013-12-12 11:32:23 |
Valerii Kravchuk |
nominated for series |
|
percona-server/5.5 |
|
2013-12-12 11:32:23 |
Valerii Kravchuk |
bug task added |
|
percona-server/5.5 |
|
2013-12-12 11:32:23 |
Valerii Kravchuk |
nominated for series |
|
percona-server/5.6 |
|
2013-12-12 11:32:23 |
Valerii Kravchuk |
bug task added |
|
percona-server/5.6 |
|
2013-12-12 11:32:35 |
Valerii Kravchuk |
percona-server/5.6: status |
New |
Confirmed |
|
2013-12-12 11:32:43 |
Valerii Kravchuk |
percona-server/5.5: status |
New |
Confirmed |
|
2013-12-12 12:17:43 |
Laurynas Biveinis |
tags |
|
doc |
|
2013-12-12 12:18:14 |
Laurynas Biveinis |
percona-server/5.5: assignee |
|
Hrvoje Matijakovic (hrvojem) |
|
2013-12-12 12:18:18 |
Laurynas Biveinis |
percona-server/5.6: assignee |
|
Hrvoje Matijakovic (hrvojem) |
|
2013-12-12 12:18:21 |
Laurynas Biveinis |
percona-server/5.5: importance |
Undecided |
Medium |
|
2013-12-12 12:18:24 |
Laurynas Biveinis |
percona-server/5.6: importance |
Undecided |
Medium |
|
2013-12-12 12:18:25 |
Laurynas Biveinis |
percona-server/5.5: status |
Confirmed |
Triaged |
|
2013-12-12 12:18:27 |
Laurynas Biveinis |
percona-server/5.6: status |
Confirmed |
Triaged |
|
2016-03-24 15:15:44 |
Laurynas Biveinis |
nominated for series |
|
percona-server/5.7 |
|
2016-03-24 15:15:44 |
Laurynas Biveinis |
bug task added |
|
percona-server/5.7 |
|
2017-08-01 06:45:58 |
Hrvoje Matijakovic |
percona-server/5.5: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
2017-08-01 06:46:03 |
Hrvoje Matijakovic |
percona-server/5.6: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
2017-08-01 06:46:08 |
Hrvoje Matijakovic |
percona-server/5.7: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|