What steps will reproduce the problem?
1. Setup RDS to Redshift replication
2. Took replicators offline
3. Configured tungsen_provision_thl with mysql sandbox
4. failed to start provisioning step
What is the expected output?
Provisions RDS instance for initial setup against Redshift
What do you see instead?
In provision_thl.log
2015-02-08T17:47:55+00:00 DEBUG >> Execute `mysqldump
--defaults-file=/opt/continuent/share/.my.alpha.cnf
--host=mysql-prod1.chh5uzdhhinu.us-east-1.rds.amazonaws.com --port=3306
--no-data --skip-triggers --add-drop-database --databases cyclope | perl -pe
's/(myisam|innodb)/Blackhole/i' >>
/home/tungsten/mysql-sandbox-stage/tungsten_provision_thl/tmp/schema.sql`
2015-02-08T17:47:55+00:00 DEBUG >> RC: 0, Result: , Errors: mysqldump: Got
error: 1044: Access denied for user 'tungsten'@'%' to database 'cyclope' when
using LOCK TABLES
Issue#2
2015-02-08T17:36:01+00:00 DEBUG >> Execute
`/home/tungsten/mysql-sandbox-stage/tungsten_provision_thl/tmp/mysqldump.sh`
2015-02-08T17:36:01+00:00 DEBUG >> RC: 0, Result: , Errors: mysqldump: Couldn't
execute 'FLUSH /*!40101 LOCAL */ TABLES': Access denied; you need (at least one
of) the RELOAD privilege(s) for this operation (1227)
What version of the product are you using?
3.0
On what operating system?
Linux Centos
Please provide any additional information below.
Notes:
Issue1: RDS doesn't support LOCK TABLES... so it appears resolution is to add
option --single-transaction
Issue2:
Similar to previous issue RDS does not support FLUSH. The mysqldump.sh is built
via tungsten_provision_thl.rb, so once I changed the command to omit:
"--master-data=2" (apparently also not needed in RDS or supported).. the
mysqldump.sh would run.
Original issue reported on code.google.com by jonas1...@gmail.com on 21 Feb 2015 at 5:14
Original issue reported on code.google.com by
jonas1...@gmail.comon 21 Feb 2015 at 5:14