| 2018-01-11 20:01:44 |
Bryce Moore |
description |
If --data-dir option is specified in pt-online-schema-change, the directory given must be writable for the executing user on the localhost that pt-online-schema-change is executed from, even if the target database is remotely. Without this, the tool fails with "directory is not writable". This prevents using pt-online-schema-change from a remote application or administrative server that is not set up as a database server.
To reproduce, run the following on a server that does not have directory "/var/lib/mysql_archive" but has connectivity to "remotehost" that does have "/var/lib/mysql_archive":
pt-online-schema-change --config ptoolkit.cfg --alter "engine=innodb" --data-dir /var/lib/mysql_archive --execute h=remotehost,D=db1,t=tb1 |
If --data-dir option is specified in pt-online-schema-change, the directory given must be writable for the executing user on the localhost that pt-online-schema-change is executed from, even if the target database is remote. Without this, the tool fails with "directory is not writable". This prevents using pt-online-schema-change from a remote application or administrative server that is not set up as a database server.
To reproduce, run the following on a server that does not have directory "/var/lib/mysql_archive" but has connectivity to "remotehost" that does have "/var/lib/mysql_archive":
pt-online-schema-change --config ptoolkit.cfg --alter "engine=innodb" --data-dir /var/lib/mysql_archive --execute h=remotehost,D=db1,t=tb1 |
|
