problem in mysql replication

[barrathi]

hai i have problem with mysql replication.
master -slave replication

and

two way replication


please can any one tell me step by step solution

thanks & regards

barrathi

[sashi]

hai i have problem with mysql replication.
master -slave replication

and

two way replication


please can any one tell me step by step solution

thanks & regards

barrathi

Hi there,

Kindly refer to below attached link for further reading & understanding, hope it helps. Good luck & Take care.

MYSQL Replication Step by step guide

[barrathi]

Hi there,

Kindly refer to below attached link for further reading & understanding, hope it helps. Good luck & Take care.

MYSQL Replication Step by step guide

thank u sashi

[barrathi]

hai sashi i have one main problem.

problem is master - slave replication is working fine but it works 30 mins to 1 hr
then it is not working.
why because is MASTER_LOG_FILE='mysql-bin.000001' this file is changing frequently

like 1hr
it shows MASTER_LOG_FILE='mysql-bin.000001'

after that
MASTER_LOG_FILE='mysql-bin.000002'

after some time it shows

MASTER_LOG_FILE='mysql-bin.000099'

this is the main problem

how do fix the master_log_file?

and if possible u can see following website


http://docs.hp.com/en/5991-7431/ar01s05.html


these are the one of the steps.

mysql> CHANGE MASTER TO
-> MASTER_HOST='master_host_name',
-> MASTER_USER='replication_user_name',
-> MASTER_PASSWORD='replication_password',
-> MASTER_LOG_FILE='recorded_log_file_name',
-> MASTER_LOG_POS=recorded_log_position;


For this example, enter the following commands:

mysql> CHANGE MASTER TO
-> MASTER_HOST='master.test',
-> MASTER_USER='osmusr',
-> MASTER_PASSWORD='osmpass',
-> MASTER_LOG_FILE='mysql-bin.000001',
-> MASTER_LOG_POS=1678;

thanks

[angst]

Hello,

I've just setup my first mysql replication this week.
and this is what i've found.

replication works prefectly *IF*, you do not add/edit/delete any thing on the slave server.
you don't need to worrie about the bin-log changing, after the first time that you point it to the log that SHOW MASTER STATUS; displays. the salve can fallow along and keep up.

what I've found is that mysql does not currently support any really two-way replication. so the solution that i've found is that, you can read from both servers, and only insert/update/delete from the master. this will keep both server sync'd up correctly.

unless any one else has a better idea, this is the best i was able to find.

hope this helps,
cheers,
-Ken

[barrathi]

thanks for your replay angst

Hello,

I've just setup my first mysql replication this week.
and this is what i've found.

replication works prefectly *IF*, you do not add/edit/delete any thing on the slave server.
you don't need to worrie about the bin-log changing, after the first time that you point it to the log that SHOW MASTER STATUS; displays. the salve can fallow along and keep up.

what I've found is that mysql does not currently support any really two-way replication. so the solution that i've found is that, you can read from both servers, and only insert/update/delete from the master. this will keep both server sync'd up correctly.

unless any one else has a better idea, this is the best i was able to find.

hope this helps,
cheers,
-Ken