Hi Alex,
we have another replication setup, i just checked that "Read_Master_Log_Pos"
and "exec_master_log_pos" has the same value.
regards
anandkl
On 7/9/07, Alex Arul Lurthu <[EMAIL PROTECTED]> wrote:
You will be taking a chance if you use Read_Master_Log_Pos: 106683511. It
is not guarantee
You will be taking a chance if you use Read_Master_Log_Pos: 106683511. It is
not guaranteed that whatever is read from master is definitely applied.
The apply of the read sqls might have stopped somewhere and in that
case Read_Master_Log_Pos
and exec_master_log_pos might be different.
--
Than
Hi Alex,
Thanks a lot,
I missed on taking the "exe_master_log position" value.
If i start from Read_Master_Log_Pos: 106683511, will it cause any harm.
regards
anandkl
On 7/9/07, Alex Arul Lurthu <[EMAIL PROTECTED]> wrote:
Anand,
If the dump was taken from the slave then the binlog positions
Anand,
If the dump was taken from the slave then the binlog positions that were
dumped out are that of the slave. Now you might do 2 things :
1. Setup a slave of your master
To do this use the binlog positions that you obtained using the
command show slave status on your slave. The master
Hi Alex,
Thank you for the response,
But i took the dump from slave and slave was in sync with master, so should
i still be doing the restore from bin-log 3 from position 311.
regards
anandkl
On 7/8/07, Alex Arul Lurthu <[EMAIL PROTECTED]> wrote:
On 7/6/07, Ananda Kumar <[EMAIL PROTECTE
On 7/6/07, Ananda Kumar <[EMAIL PROTECTED]> wrote:
-- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.03',
MASTER_LOG_POS=311;
As see in the mysqldump is saying to start recovery from bin-log file "'
mysql-bin.03'" and position="MASTER_LOG_POS=311",
You need to use the positions specif
