core dump - Can't connect to MySQL server on '10.0.2.148' (111) at /usr/local/bin/pt-online-schema-change line 2262
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have a unique topology with replication.
I am attempting to attach to a Master that is ALSO a SLAVE..
I have a dsns table set up on 10.0.2.148 that has the one entry (10.0.2.147) - the slave
There is a Grand MASTER 10.0.2.150
So there is a Master-Slave 10.0.2.149 (has replication filters)
The server I am attempting to connect to (10.0.2.148) and execute schema changes on has one Slave Host replicating -> ASE2TestVM (10.0.2.147)
I run a --dry-run and there are NO issues. (Debug mode tells me nothing extra???)
I run in --execute mode and it always end up with the same....A core dump and it exits. I Keep getting a message that it cannot connect to MySQL Server on '10.0.2.148' (111) at /usr/local/
Once this happens....I notice the connection has dropped and that the SLAVE has STOPPED Replication on 10.0.2.148
The Slave host under that master/slave (10.0.2.147) - is fine.....it is still replicating.
A core dump happens and I have to clean up the triggers and the temp table manually.
The command I am running is as follows:
>pt-online-
Found 1 slaves:
ASE2TestVM
Will check slave lag on:
ASE2TestVM
Operation, tries, wait:
copy_rows, 10, 0.25
create_triggers, 10, 1
drop_triggers, 10, 1
swap_tables, 10, 1
update_
Altering `ATData`
Creating new table...
Created new table ATData._Retest_new OK.
Altering new table...
Altered `ATData`
2015-07-08T15:28:46 Creating triggers...
2015-07-08T15:28:46 Created triggers OK.
2015-07-08T15:28:46 Copying approximately 5406492 rows...
2015-07-08T15:28:49 Dropping triggers...
2015-07-08T15:28:49 Error dropping trigger: DBI connect(
.0.2.148' (111) at /usr/local/
2015-07-08T15:28:49 Error dropping trigger: DBI connect(
.0.2.148' (111) at /usr/local/
2015-07-08T15:28:49 Error dropping trigger: DBI connect(
.0.2.148' (111) at /usr/local/
2015-07-08T15:28:49 To try dropping the triggers again, execute:
DROP TRIGGER IF EXISTS `ATData`
DROP TRIGGER IF EXISTS `ATData`
DROP TRIGGER IF EXISTS `ATData`
`ATData`.`Retest` was not altered.
Segmentation fault (core dumped)
dgregg@
tags: | added: pt-online-schema-change |
Here is the dry-run
no issues...
dgregg@ Slave6vm: /usr/local/ bin$ pt-online- schema- change --recursion- method= dsn=h=10. 0.2.148, D=percona, t=dsns --nocheck- replication- filters --check-interval=2 --max-lag=10 --critical-load Threads_running=15 --alter "modify ExtraText1 varchar(256);" h=10.0. 2.148,D= ATData, t=Retest, u=root, p=pswd- -dry-run foreign_ keys, 10, 1 .`_Retest_ new` OK. Slave6vm: /usr/local/ bin$
Operation, tries, wait:
copy_rows, 10, 0.25
create_triggers, 10, 1
drop_triggers, 10, 1
swap_tables, 10, 1
update_
Starting a dry run. `ATData`.`Retest` will not be altered. Specify --execute instead of --dry-run to alter the table.
Creating new table...
Created new table ATData._Retest_new OK.
Altering new table...
Altered `ATData`
Not creating triggers because this is a dry run.
Not copying rows because this is a dry run.
Not swapping tables because this is a dry run.
Not dropping old table because this is a dry run.
Not dropping triggers because this is a dry run.
2015-07-08T15:58:54 Dropping new table...
2015-07-08T15:58:54 Dropped new table OK.
Dry run complete. `ATData`.`Retest` was not altered.
dgregg@
#