At this point, I see this on the master
mysql> show master status; Empty set (0.00 sec)
and this on the slave:
mysql> show slave status\G
*************************** 1. row ***************************
Master_Host: master-db
Master_User: repl
Master_Port: 3306
Connect_retry: 60
Master_Log_File: carbon-bin.000009
Read_Master_Log_Pos: 201392116
Relay_Log_File: silicon-relay-bin.000007
Relay_Log_Pos: 4
Relay_Master_Log_File: carbon-bin.000009
Slave_IO_Running: No
Slave_SQL_Running: Yes
Replicate_do_db:
Replicate_ignore_db:
Last_errno: 0
Last_error:
Skip_counter: 0
Exec_master_log_pos: 201392116
Relay_log_space: 4which I think means my replications long past the point of retrieval.
I'm pretty well reconciled to taking my system out of production, copying all the
databases from the master to the slave, dropping the binlogs and restarting
the replication.
I have 2 questions:
1. Can I safely delete the binlogs and clear the binlog index by hand? 2. How can I regulate the size of the binlogs to something manageable?
TIA for your help.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
