Tag Info

New answers tagged

0

I do not think that that bug is your problem, as it was solved in a previous release than the one you are using. I think that the problem you are facing is doing ALTER an BULK updates though the binary log, which will block and take a long time to execute in both cases. To avoid that, I would recommend, whenever you execute such operations, to do it ...


2

Bucardo is the standard tool for this sort of job. It's well tested to run when the two servers are disconnected from each other for a while. You could use any master/master replication approach instead: Londiste, Slony, or the early release of BDR from 2ndQuadrant. With the network setup you've described, you will be hard pressed to avoid race ...


0

Error: Last_SQL_Errno: 1594 Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. This error means that either the master log file is corrupted or the relay log file is corrupted. Before doing anything backup all your databases, logs, image servers, repeat, several times, and only continue at your own risk. First run "show ...


0

When you see the Seconds_Behind_Master that high, I look at the following: Relay_Log_Space: 8179978166 You have 7.6182GB of relay logs to process. Master_Log_File: mysql-bin.000173 Relay_Master_Log_File: mysql-bin.000093 This tell me that you have read up to mysql-bin.000173, but you are currently processing things from the mysql-bin.000093. This ...


1

It is feasible (you can chain-replicate more than 2 servers), but unnecessary: you can forward access using a VPN or, if you do not want to set that up, with simple SSH port forwarding. This applies even if you have a Windows server -you can install OpenSSH or any other SSH software or application that allows you to forward ports. SSH is the standard ...


2

First of all, I dislike your setup. When Server B fails, the Server C will not be in replication anymore. If you want to be safe, that the data is on every server in sync, you should try to use a cluster. A cluster is minimum 3 servers and would fit your environment. Next question for me is, why don't you use just one master (Server A) and two slaves ...


0

If you are using InnoDB with the option innodb_file_per_table option off (by default on MySQL 5.1 and before), you need to stop the server after the dump (make sure you are not using innodb_fast_shutdown = 2), then delete at least the ibdata1, ib_logfile0, ib_logfile1 and your database directory and finally restart MySQL and import only the final truncated ...


0

OK, here is how I ended up addressing this. I basically wrote a script to compare row counts between tables on publisher and the distributor. One per-requisite is to have a linked server between the two servers. In my case it is called "distributor_ls" (since distributor is on the same server as the subscriber). First part of the script gather information ...


2

My explanation is that sp_publication_validation validates a Publication: set of Articles sent by Publisher and received by Subscriber. Since there were no data corruption in transit this SP does not report any errors. To detect differences in replicated tables use SP_TABLE_VALIDATION. Either returns rowcount or checksum information on a table or ...


1

I found the problem. The slave was trying to connect to port 7 instead of port 3306 for some reason. I had to manually specify that as part of CHANGE MASTER TO command and add MASTER_PORT=3306 and it works perfectly now.


1

I actually managed to do it with engine=FEDERATED to get the syncing done. No need to replicate and all info is up to date. Site specific fields are captured in a seperate table.


2

The issue is covered in this detailed blog. In short, the master and the standby servers must all have archive_mode = on and an archive_command, until 9.3 which removes this requirement.


0

Let me give you a very broad piece of advise: I think you are trying optimisation in the wrong way. You are doing "We have spare memory, let's use it for something else" (which is otherwise very lucky and many people will envy you) instead of "let's identify our bottleneck and fix that with our resources". I am not telling you that your idea is wrong, but ...


0

Only the master would need a fixed IP address, since its the slaves that pulls data. You say UPDATE the master in your question, but it is not possible for a slave to update a master, unless you have a MASTER to MASTER replication setup. As you are using the word slave, then that assumes that the Slave server only pulls data but doesn't update the Master. ...


2

That isn't a problem, it's by design. If you don't want transactions to wait until a synchronous replica acknowledges a commit, then you don't want synchronous replication. You want async replication and should simply remove the synchronous_standby_names option. What good would synchronous replication be if it gave up when no replica was reachable? "I ...


1

With a single write master <> master setup, I don't need to worry about setting the auto_increment_offset correct? Yes, you are right. I have setup Master-Master setups for years with one Write Master. I never touched the auto_increment options. Never had an incident. Does MySQL replicate all databases by default, or do I need to explicitly ...


1

I want to make sure replication start as soon as server starts . You can't. The server needs to start up, and it can only establish a streaming replication connection when it's up and ready. I want to know why this happens Because there's no reason not to accept connections before streaming replication begins. Among other things, if you're using ...


0

If you want the binlog file and position, just include --master-data. According to the MySQL Documentation on mysqldump's --master-data option Use this option to dump a master replication server to produce a dump file that can be used to set up another server as a slave of the master. It causes the dump output to include a CHANGE MASTER TO ...


2

If a relay slave (a.k.a. Distribution Master) is using nothing but the BLACKHOLE storage engine for application tables, you really should not have to tune anything for MyISAM or InnoDB since there are no data or index pages to cache. You will have a nominal amount of disk I/O (mostly reads) since the .frm file for every BLACKHOLE is still accessed for ...


0

The whole point of snapshot is to provide a point in time copy of the articles involved in replication. It does it when generating the snapshot files from the publisher by locking the tables until the snapshot is finished for that particular article. You should plan to reinitialize during less activity time of your server. Is there anyway to do this ...


0

Replication setup on a windows server is equivalent to doing it in other systems: The official manual provides you a detailed guide. In short: Configure on both servers a different server-id, and activate the binary log on the master. If it is not already done, the most typical way to do that is modify the my.ini file and restart the service (net restart ...


0

Look at the Slave Status Master_Log_File: .001746 <<--------------- Read_Master_Log_Pos: 123599834 <<------------- Relay_Log_File: XXXXXXX.000014 Relay_Log_Pos: 290086986 Relay_Master_Log_File: .001733 <<--------------- Slave_IO_Running: Yes Slave_SQL_Running: Yes ...


0

I find that executing a FLUSH command helps in refreshing the SHOW SLAVE HOSTS output. It isn't deterministic; I sometimes need to execute two or three FLUSH commands, but it certainly refreshes. I found that either FLUSH LOGS or FLUSH STATUS do the job.


0

Yes, Amazon uses standard replication for its instances. Not only it is documented here, but also is proven with the fact that you can replicate from and to MySQL instances outside of RDS. No need for any extra packages/software, a standard MySQL server can be a master and/or a slave with the appropriate configuration and preparation. Yes, if you run ...



Top 50 recent answers are included