Thanks for the reply.
I didn't explain properly :)
A diagram should help:
|--------|
|-----| 1 |----| 2 | |--------|
|stage| --> |prod| --> |-| |--------|
|-----| |----| |-|replicas|
|--------|
'stage' is a staging mysql instance, where changes are made all the
time. When the data is ready for production, it needs to be pushed to
'prod', at which time it will be replicated out to all the slaves.
Step 2 is covered by the answer to my previous question.
Step 1 is really my question. My need is that somehow a table already
existing on stage can be copied/replicated/etc over to prod, but _only_
when requested, and then immediately.
Any thoughts?
Thanks,
Ross
On Tue, 2003-06-03 at 12:07, Dathan Vance Pattishall wrote:
> -->-----Original Message-----
> -->From: Ross Simpson [mailto:[EMAIL PROTECTED]
> -->Sent: Tuesday, June 03, 2003 10:31 AM
> -->To: [EMAIL PROTECTED]
> -->Subject: table copying/replication
> -->
> -->Hello,
> -->
> -->I have a need for fast copying of a specific table from a master
> mysql
> -->server to a number of slave servers (say 5).
> Create the table on the master and if the master and slave config is
> working then the same table will be on the slave.
>
>
> -->
> -->The database in question could potentially have up to 2000 tables,
> and
> -->at any time, one of those tables would need to be copied to all 5 of
> the
> -->slaves, upon command of the master.
> Make sure you have enough inodes that's 6000 files that will be opened.
> Also set your ulimit high enough to open all the files.
>
> Replication will perform the same action on the slaves as initiated by
> the master. There is no need for a copy.
>
> -->I also looked at doing table copies (insert into .. select * from
> ..),
> -->but these seem pretty slow.
> It's building the index on the fly as well, if there are indexes on the
> dst table. It does have to scan the src table and for every row insert
> it into the dst table. You can tweak you're my.cnf values to make that
> operation happen faster.
>
> -->
> -->Has anyone solved this problem before? Any ideas that would help
> out?
> -->
>
> Yes, the mysql team with replication.
>
> -->
> -->--
> -->Ross Simpson <[EMAIL PROTECTED]>
> -->MapQuest.com
> -->
> -->
> -->--
> -->MySQL General Mailing List
> -->For list archives: http://lists.mysql.com/mysql
> -->To unsubscribe:
> -->http://lists.mysql.com/[EMAIL PROTECTED]
>
--
Ross Simpson <[EMAIL PROTECTED]>
MapQuest.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
