[Maria-discuss] upgrading from mariadb 5.5.31 to mariadb 5.5.32 with innodb engine
Hello!
few days ago we realized we got cached by the bug MDEV-4754 [1] . Today mariadb 5.5.32 has been released but among the notable Information the mysql bug #69623 [2] is mentioned in case you have the table using the Innodb engine.
per our information:
| innodb_data_file_path | ibdata1:100M:autoextend | | innodb_data_home_dir | /var/lib/mysql/innodb | | innodb_file_per_table | ON | | innodb_version | 5.5.31-MariaDB-30.2 |
I think we fit exactly in that scenario but I need some help to confirm this and be sure can *upgrade* without issues or that we should wait for another release that fix this.
Any clue?
Thanks!
[1] https://mariadb.atlassian.net/browse/MDEV-4754 [2] http://bugs.mysql.com/bug.php?id=69623 -- Gabriel Sosa Sometimes the questions are complicated and the answers are simple. -- Dr. Seuss
i updated some servers here, and in my case is ok
2013/7/18 Gabriel Sosa sosagabriel@gmail.com
Hello!
few days ago we realized we got cached by the bug MDEV-4754 [1] . Today mariadb 5.5.32 has been released but among the notable Information the mysql bug #69623 [2] is mentioned in case you have the table using the Innodb engine.
per our information:
| innodb_data_file_path | ibdata1:100M:autoextend | | innodb_data_home_dir | /var/lib/mysql/innodb | | innodb_file_per_table | ON | | innodb_version | 5.5.31-MariaDB-30.2 |
I think we fit exactly in that scenario but I need some help to confirm this and be sure can *upgrade* without issues or that we should wait for another release that fix this.
Any clue?
Thanks!
[1] https://mariadb.atlassian.net/browse/MDEV-4754 [2] http://bugs.mysql.com/bug.php?id=69623 -- Gabriel Sosa Sometimes the questions are complicated and the answers are simple. -- Dr. Seuss
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
On 7/18/2013 2:36 PM, Gabriel Sosa wrote:
Hello!
few days ago we realized we got cached by the bug MDEV-4754 [1] . Today mariadb 5.5.32 has been released but among the notable Information the mysql bug #69623 [2] is mentioned in case you have the table using the Innodb engine.
per our information:
| innodb_data_file_path | ibdata1:100M:autoextend |
The MySQL bug 69623 refers to having two or more tablespaces. You only have one. If you had more it would look like: innodb_data_file_path | ibdata1:100M;ibdata2:100M:autoextend
Also, as noted in the Release Notes, if you are using XtraDB, the default, you are not affected. If you load the innodb_plugin, you still wouldn't be in your setup, but others may be.
Brian
Hi Brain, I think Gabriel talked about memory leak in query cache + xtradb (or innodb)
Elena put this comment in JIRA:
The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103), and MariaDB 5.5.32 includes XtraDB 5.5.32. We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,
and reporter (Gabriel), send this comment: Gabriel Sosahttps://mariadb.atlassian.net/secure/ViewProfile.jspa?name=pendexgabo added a comment - Today 14:01 excellent! perfect. Thanks for your time
Gabriel, i made this: try a small database with 5.5.32 and check if bug persist, if not, upgrade production servers without problems i updated 3 production servers and they are working normally without the bug and query cache enabled, i'm using xtradb (not innodb plugin)
@Spadim thanks but in fact I'm referring to this
Other Notable Information
- Includes XtraDB https://kb.askmonty.org/en/xtradb/ from Percona Server-5.5.32-rel31.0
- As long as XtraDB is used, MariaDB 5.5.32https://kb.askmonty.org/en/mariadb-5532-release-notes/is not affected by MySQL Bug #69623 http://bugs.mysql.com/bug.php?id=69623 (multi-file tablespaces do not work after an upgrade).
I know that the bug MDEV-4754https://mariadb.atlassian.net/browse/MDEV-4754was fixed but upgrading I found out that I could go for a worse scenario if the bug 69623 http://bugs.mysql.com/bug.php?id=69623 affects me. so my question is how can I be sure that I won't be affected by the bug 69623http://bugs.mysql.com/bug.php?id=69623
make sense?
On Thu, Jul 18, 2013 at 4:12 PM, Roberto Spadim roberto@spadim.com.brwrote:
Hi Brain, I think Gabriel talked about memory leak in query cache + xtradb (or innodb) Elena put this comment in JIRA:
The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103), and MariaDB 5.5.32 includes XtraDB 5.5.32. We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,
and reporter (Gabriel), send this comment: Gabriel Sosahttps://mariadb.atlassian.net/secure/ViewProfile.jspa?name=pendexgabo added a comment - Today 14:01 excellent! perfect. Thanks for your time
Gabriel, i made this: try a small database with 5.5.32 and check if bug persist, if not, upgrade production servers without problems i updated 3 production servers and they are working normally without the bug and query cache enabled, i'm using xtradb (not innodb plugin)
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
i only have one table space, and no errors here when upgrading i think it's better copy the innodb file (or dump or hot backup) and try in a test machine and after, upgrade and try again the production server
Am 18.07.2013 21:16, schrieb Gabriel Sosa:
@Spadim thanks but in fact I'm referring to this
* As long as XtraDB is used, MariaDB 5.5.32 is not affected by MySQL Bug #69623 (multi-file tablespaces do not work after an upgrade)
I know that the bug MDEV-4754was fixed but upgrading I found out that I could go for a worse scenario if the bug 69623 affects me. so my question is how can I be sure that I won't be affected by the bug 69623
simply use XtraDB?
@Reindl AFAIK I'm using XtraDB. We don't have the InnoDb plugin installed. Should I assume we are safe?
+--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+ | Engine | Support | Comment | Transactions | XA | Savepoints | +--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+ | CSV | YES | CSV storage engine | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | MyISAM | YES | MyISAM storage engine | NO | NO | NO | | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | FEDERATED | YES | FederatedX pluggable storage engine | YES | NO | YES | | ARCHIVE | YES | Archive storage engine | NO | NO | NO | | InnoDB | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES | YES | YES | | PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO | | Aria | YES | Crash-safe tables with MyISAM heritage | NO | NO | NO | +--------------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
Saludos
On Thu, Jul 18, 2013 at 4:25 PM, Reindl Harald h.reindl@thelounge.netwrote:
Am 18.07.2013 21:16, schrieb Gabriel Sosa:
@Spadim thanks but in fact I'm referring to this
* As long as XtraDB is used, MariaDB 5.5.32 is not affected by MySQL Bug
#69623
(multi-file tablespaces do not work after an upgrade)
I know that the bug MDEV-4754was fixed but upgrading I found out that I could go for a worse scenario if the bug 69623 affects me. so my question is how can I be sure that I won't be affected by the bug
69623
simply use XtraDB?
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 18.07.2013 21:33, schrieb Gabriel Sosa:
@Reindl AFAIK I'm using XtraDB. We don't have the InnoDb plugin installed. Should I assume we are safe?
On Thu, Jul 18, 2013 at 4:25 PM, Reindl Harald <h.reindl@thelounge.net mailto:h.reindl@thelounge.net> wrote:
Am 18.07.2013 21:16, schrieb Gabriel Sosa: > @Spadim thanks but in fact I'm referring to this > > * As long as XtraDB is used, MariaDB 5.5.32 is not affected by MySQL Bug #69623 > (multi-file tablespaces do not work after an upgrade) > > I know that the bug MDEV-4754was fixed but upgrading I found out > that I could go for a worse scenario if the bug 69623 affects me. > so my question is how can I be sure that I won't be affected by the bug 69623
simply use XtraDB?
so besides the fact that you should *not* top-post after get a reply at bottom what was the intention of your post?
On Thu, Jul 18, 2013 at 5:14 PM, Reindl Harald h.reindl@thelounge.netwrote:
Am 18.07.2013 21:33, schrieb Gabriel Sosa:
@Reindl AFAIK I'm using XtraDB. We don't have the InnoDb plugin
installed. Should I assume we are safe?
On Thu, Jul 18, 2013 at 4:25 PM, Reindl Harald <h.reindl@thelounge.net<mailto:
h.reindl@thelounge.net>> wrote:
Am 18.07.2013 21:16, schrieb Gabriel Sosa: > @Spadim thanks but in fact I'm referring to this > > * As long as XtraDB is used, MariaDB 5.5.32 is not affected by
MySQL Bug #69623
> (multi-file tablespaces do not work after an upgrade) > > I know that the bug MDEV-4754was fixed but upgrading I found out > that I could go for a worse scenario if the bug 69623 affects me. > so my question is how can I be sure that I won't be affected by
the bug 69623
simply use XtraDB?
so besides the fact that you should *not* top-post after get a reply at bottom what was the intention of your post?
apologizes for the top-post and for some reason the message got broken...
@Reindl you said
simply use XtraDB?
My questions is:
If per `show engines` I can see we are using Percona-XtraDB replacing the InnoDB engine, can we assume it is safe to upgrade?
show engines output:
| InnoDB | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
I hope this make sense now.
Thanks
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
participants (4)
-
Brian Evans -
Gabriel Sosa -
Reindl Harald -
Roberto Spadim