Not the answer you need?
Register and ask your own question!

pt-online-schema-change segfaults on AWS RDS

jpedrojpedro EntrantInactive User Role Beginner
Can you help me please understand why pt-osc fails when I run on Amazon AWS RDS both for --alter "Engine=InnoDB" and for --alter "ADD name CHAR(30)" ?

Thanks in advance!

---

[email protected]:~$ pt-online-schema-change --alter="Engine=InnoDB" --host=rds-x.eu-west-1.rds.amazonaws.com --user=x --password=x D=db,t=tb --execute --recursion-method=none --statistics
No slaves found. See --recursion-method if host ip-x-x-x-x has slaves.
Not checking slave lag because no slaves were found and --check-slave-lag was not specified.
Operation, tries, wait:
copy_rows, 10, 0.25
create_triggers, 10, 1
drop_triggers, 10, 1
swap_tables, 10, 1
update_foreign_keys, 10, 1
Altering `db`.`tb`...
Creating new table...
Created new table db._tb_new OK.
Altering new table...
Altered `db`.`_tb_new` OK.
2014-07-21T13:55:31 Creating triggers...
2014-07-21T13:55:31 Dropping triggers...
2014-07-21T13:55:31 Dropped triggers OK.
2014-07-21T13:55:31 Dropping new table...
2014-07-21T13:55:32 Dropped new table OK.
# Event Count
# ============= =====
# INSERT 0
# retry_fail 1
# unknown_error 1
`db`.`tb` was not altered.
Segmentation fault (core dumped)

Comments

  • jpedrojpedro Entrant Inactive User Role Beginner
    FYI: This is the table structure:


    mysql > show create table tb \G
    *************************** 1. row ***************************
    Table: tb
    Create Table: CREATE TABLE `tb` (
    `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
    `value` int(10) unsigned NOT NULL,
    `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`)
    ) ENGINE=MyISAM AUTO_INCREMENT=4 DEFAULT CHARSET=utf8
    1 row in set (0.00 sec)
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.