XtraDB-cluster-56 crashed on database update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I found some strange bug, Percona-
Current setup - db_server-1:
- FreeBSD 9.1-RELEASE-p22 amd64
- percona55-
- rt42-4.2.1_1 (request tracker from bestpractial.com)
New setup with 3 x Nodes:
- lates CentOS release 6.6 (Final) 2.6.32-
- Percona-
- rt-4.2.9
Steps:
1. dump database with innobackupex on db_server-1
2. copy dump to Node1
3. restore dump with “innobackupex --copy-back” and chown mysql:mysql /home/mysql
4. bootstrap first Node1 server
5. mysql-upgrade for upgrade database from 55 to 56
6. cd src/rt-4.2.9; ./configure ; make install; make upgrade-database (for upgrade RT database from 4.2.1 to 4.2.9)
7. crashed on 4.2.2 (corefile core.35841 in archive )
8. bootstrap Node1 server again
9. run “make upgrade-database” again, from 4.2.2 to 4.2.9
7. crashed on 4.2.6 (corefile core.36765 if need I can provide this file too)
8. bootstrap Node1 server again
9. run “make upgrade-database” again, from 4.2.6 to 4.2.9
7. not crashed
10. found what in table Users(example), only 90000 records, when on db_server-1 - 96979, so on step 7 we lost some data in database, what is not good
Same steps(1-4,6) on same server but with Percona-
Screenshot with crash: https:/
core.35841: https:/
my.cnf: https:/
error.log: https:/
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXC-1764