MySQL Master-Slave Configuration: Don't Replicate a Row of a Table? Post: 302461246

Sponsored Content

Top Forums Web Development MySQL Master-Slave Configuration: Don't Replicate a Row of a Table? Post 302461246 by Neo on Saturday 9th of October 2010 11:58:51 AM

10-09-2010

Administrator

Quote:

Originally Posted by radoulov

Neo,
I assume these options are static so you could take a dump of the production db (use --master-data), then import the data in the slave, update the rows on the slave with the proper configuration and then start the replication. As far as those rows remain untouched on the master, the slave configuration will remain valid.

Thanks!

That is exactly what I've been doing (manually). The part I wish to avoid is editing the slave each time I upload the masterdump data into the slave.

In addition to the static data, some data is dynamic, and I want the data on the slave and master to remain unique to each other (secondary requirement, not a show stopper).

For example, when replicating this vB forum, static information is, for example, the URL of the forum (they are different in the test environment), and dynamic information is the number of users on the site. This information comes from a table called "datastore" which contains rows with various static configuration / option data and dynamic data, like who is on the site, spiders, number of users on line, etc.

If I replicate the entire datastore table, I have problem when I turn off vB plugins on the slave that remain on on the master. Yes, I can work around by manually updating the configuration on the slave each time; but then if I turn off a plugin (or turn on a dormant one) on the master, it will update the slave, which I don't want.

That's why I was hoping there was some way to just exclude some rows in the datastore table from replicating.

Also, I thought about perhaps instructing the slave to permanently lock the rows so they can't be effected by uploading a dump or master replication.

Maybe that will work?

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NIS master / slave problems

Our NIS master server went down. We have since fixed it and brought it back up. However all of are machines still point to the slave server when looking at it with ypwhich. My question is how do i point the servers back to the master. Frank

2. SCO

master and slave in lan network

hello , i setup a lan network , but i don't know how configure master and slave in the lan network please help me:confused:

3. AIX

Slave NIS server configuration change

Hello Everybody, I have a question regarding SLAVE NIS SERVER in aix. We are using NIS master of Sun Solaris 9.0 which is on different subnet i.e. 10.197.93.0. And Our slave server is having AIX 5.3 installed which is on 10.207.13.0 subnet. I have a query regarding its name and ip address...

4. Shell Programming and Scripting

mysql how to select a specific row from a table

5. Programming

Asynchronous communication between master and slave threads

I am writing a process that has a master thread and a set of slave threads. Master thread is supposed to get jobs dynamically and assign to slave thread which is free. Master also get results back from slaves once a job is done. The number of slaves should be adjustable dynamically based on job...

6. UNIX Desktop Questions & Answers

How can I replicate master master and master master MySQL databse replication and HA?

I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database. For this I have created two...

7. Programming

How to wait the slave to be finished first then execute the master--MPI C++?

Hi, How to wait the slave to be finished first then execute the master? Can someone give me the specific function? Or the detailed example. Thanks~

8. IP Networking

DNS question about initial Master/Slave setup

Hey everyone. I'm creating a DNS master/slave server set up. I have the configurations all done I believe, the master has the required zone file, and the named.conf file has the allow transfer and allow query stuff set. The slave has it's own configs set. My question is that when initially...

LEARN ABOUT LINUX

ndb_delete_all

NDB_DELETE_ALL(1)					       MySQL Database System						 NDB_DELETE_ALL(1)

NAME

       ndb_delete_all - delete all rows from an NDB table

SYNOPSIS

       ndb_delete_all options

DESCRIPTION

       ndb_delete_all deletes all rows from the given NDB table. In some cases, this can be much faster than DELETE or even TRUNCATE TABLE.
	       Usage

	   ndb_delete_all -c connect_string tbl_name -d db_name

       This deletes all rows from the table named tbl_name in the database named db_name. It is exactly equivalent to executing TRUNCATE
       db_name.tbl_name in MySQL.

       The following table includes options that are specific to ndb_delete_all. Additional descriptions follow the table. For options common to
       most MySQL Cluster programs (including ndb_delete_all), see Options Common to MySQL Cluster Programs(1).

       Table 17.16. ndb_delete_all Options and Variables: MySQL Cluster NDB 7.2
       +--------------------------+-----------------------------------+-------------------------------------+
       |Format			  | Description 		      | Added / Removed 		    |
       +--------------------------+-----------------------------------+-------------------------------------+
       |			  | Name of the database in which the | 				    |
       |       --database=dbname, | table is found		      |        All MySQL 5.5 based releases |
       |			  |				      | 				    |
       |       -d		  |				      | 				    |
       +--------------------------+-----------------------------------+-------------------------------------+
       |			  | Perform the delete in a single    | 				    |
       |       --transactional,   | transaction (may run out of       |        All MySQL 5.5 based releases |
       |			  | operations) 		      | 				    |
       |       -t		  |				      | 				    |
       +--------------------------+-----------------------------------+-------------------------------------+
       |			  | Run tup scan		      | 				    |
       |       --tupscan	  |				      |        All MySQL 5.5 based releases |
       +--------------------------+-----------------------------------+-------------------------------------+
       |			  | Run disk scan		      | 				    |
       |       --diskscan	  |				      |        All MySQL 5.5 based releases |
       +--------------------------+-----------------------------------+-------------------------------------+

       o   --transactional, -t

	   Use of this option causes the delete operation to be performed as a single transaction.

	       Warning
	       With very large tables, using this option may cause the number of operations available to the cluster to be exceeded.

COPYRIGHT

       Copyright (C) 1997, 2014, Oracle and/or its affiliates. All rights reserved.

       This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as
       published by the Free Software Foundation; version 2 of the License.

       This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation,
       Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.

SEE ALSO

       For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online
       at http://dev.mysql.com/doc/.

AUTHOR

       Oracle Corporation (http://dev.mysql.com/).

MySQL 5.5							    01/30/2014							 NDB_DELETE_ALL(1)