Tag Info

New answers tagged

0

Best is to to : show grants for user@'10.%' ; each user on the original server. Then apply them to the new. Or you can use pt-show-grants -hhostname -u -p which will list all the grants. You can do that in one line of code: pt-show-grants -horigalHost -u -p | mysql -hnewHost -u -p


1

It looks that server lookup is taking time while searching for the host over the network and in order to minimize the lookup time add the entries in hosts file as entries in hosts file (/etc/hosts) does minimize the lookup time.


0

I recently did some extensive benchmarks on Percona XtraDB Cluster 5.6.21-70 and noticed a degradation after 32 threads when running transaction (insert, update, delete) against the Cluster. I then run the test against 1 node only and the degradation at 32 Threads went away. Instead of pointing your App to the Cluster, point it to a dedicated Node. We use ...


0

I think you are not alone with this issue. We stopped the multi-master replication and instead beefed up RAID and XtraBackup and no issues with 5.5 or 5.6. I have read that once you're using the wsrep and clustering, however, these issues creep in. Unsure if they have a solution yet but your best bet may be to follow this thread: ...


0

Master Master should be possible in DR too. Basically what you really have is a Master - Slave with Slave ready to become a master upon failover. So in Location 1: Master Active <--> Macter Passive Location 2: Master Active <--> Macter Passive Master Active in Location 1 should replicate to Master Active in Location 2. Make sure they all have bin ...


1

Active-Passive master-master is a good setup but I have seen SUPER (humans)users writing on slave without setting sql_log_bin. (Though super_read_only in 5.7 will change things around this.) Anyways, following is possible and works. ProdActiveMaster<---->ProdPassiveMaster | | | \/ DRmaster----->DRSlave So you know now that another master-master ...


0

1 Stop the slave on the first master mysql> STOP SLAVE; If the second master becomes a read only then the first master should no longer replicate from it. 2 Change the 2nd master's configuration to read only. mysql> SET GLOBAL READ_ONLY=1; Add read_only=1 to my.cnf for the next restart Read Only variable 3 Unlock the tables on the second ...


1

I'm not sure why you are getting that error. I have 2 solutions. The solutions will give you an error if your data truly can't be converted to unsigned bigint. ALTER TABLE `order_item_units` ADD COLUMN `parent_id2` BIGINT(255) UNSIGNED AFTER `parent_id`; UPDATE `order_item_units` SET `parent_id2` = `parent_id`; SELECT * FROM `order_item_units` WHERE ...


0

In this scenario I'd suggest sharding the clusters by functionality. If you have some tables with heavy load, maybe these tables diserve to have its own cluster. You could have a 3/5 nodes Galera cluster for this table, another 3 nodes Galera cluster for the rest of tables and the 1/3 rest of nodes to scale reads if needed. Of course, you could also shard ...


3

I can see why Oracle RAC can handle split brain and PXC cannot. What separates them in their architecture and data storage. In what ways ??? Oracle RAC All RAC Instances deal with only one set of database files Each RAC Instance has its own Log Buffer and LGWR (Log Writer) process Writes to any Oracle RAC instance, even on nodes that go down temporarily, ...


1

Seconds_Behind_Master is the difference between the timestamps a statement was most recently downloaded by the IO_THREAD and when it was most recently executed. I'd highly recommend pt-heartbeat. pt-heartbeat is a two-part MySQL and PostgreSQL replication delay monitoring system that measures delay by looking at actual replicated data. This avoids ...



Top 50 recent answers are included