Sponsored Content
Full Discussion: Mysql replication
Operating Systems Linux Mysql replication Post 302874995 by andriesh on Monday 18th of November 2013 08:25:59 AM
Old 11-18-2013
Mysql replication

Need to recover a replication broken error on the mysql slave server.
I want to force it to resend the binlog file from the begining.
What is the correct value for the:
Code:
MASTER_LOG_POS

?
0, 1 or 107 ?
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

dns replication

my primary dns server is not replicating to secondary. i dont know why. i am running solaris 2.6 on both servers. what should i do?:confused: (2 Replies)
Discussion started by: lealyz
2 Replies

2. Web Development

MySQL Replication Issues: Duplicate Key Error

Lately my attention has been focused on distributed MySQL database replication to other web servers. All was going well, but then I noticed the replication would stop and there were there "Duplicate Primary Key" errors in SHOW SLAVE STATUS; I started to trace these down and noticed that this... (2 Replies)
Discussion started by: Neo
2 Replies

3. Shell Programming and Scripting

Strategical Shell Scripting For MySql Replication

Hi to all guyz , As i'm new to Shell scripting i was been working out to write a shell script for mysql Replication for multiple slave master architecture.i have done the process up with a script of 200 lines but still there are some things which can make my script more effective so i want your... (5 Replies)
Discussion started by: kgrvamsi
5 Replies

4. Red Hat

Openldap 2.4.31 replication

Hi, I have done setup for openldap master and slave. Its working fine and replicating also. But it is working only with plane text password in syncrepl . How we can use encrypted password here also like we are using in rootpw ? Below portion is working. syncrepl rid=101 ... (3 Replies)
Discussion started by: Priy
3 Replies

5. 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... (0 Replies)
Discussion started by: Palak Sharma
0 Replies
SYNC_CLIENT(8)						      System Manager's Manual						    SYNC_CLIENT(8)

 *

NAME
sync_client - client side of the synchronization (replication) engine SYNOPSIS
sync_client [ -v ] [ -l ] [ -z ] [ -C config-file ] [ -S servername ] [ -f input-file ] [ -F shutdown_file ] [ -w wait_interval ] [ -t timeout ] [ -d delay ] [ -r ] [ -u ] [ -m ] [ -s ] objects... DESCRIPTION
Sync_client is the client side of the replication system. It runs on the client (master) system and connects to the target (replica) sys- tem and generates an appropriate sequence of transactions to synchronize the replica system with the master system. OPTIONS
-v Verbose mode. -l Verbose logging mode. -o Only attempt to connect to the backend server once rather than waiting up to 1000 seconds before giving up. -z Enable compress. If you set 'sync_compress' in the imapd.conf or pass -z to sync_client, the replication protocol will attempt to enable deflate compression on the connection. -C config-file Read configuration options from config-file. -S servername Tells sync_client which server to communicate with. Overrides the sync_host configuration option. -f input-file In mailbox or user replication mode: provides list of users or mailboxes to replicate. In rolling replication mode, specifies an alternate log file (sync_client will exit after processing the log file). -F shutdown-file Rolling replication checks for this file at the end of each replication cycle and shuts down if it is present. Used to request nice clean shutdown at first convenient point. The file in question is removed on shutdown. Overrides sync_shutdown_file option in imapd.conf -w interval Wait this long before starting. Typically used so that we can attach a debugger to one end of the replication system or the other. -t timeout Timeout for single replication run in rolling replication. sync_client will negotiate a restart after this many seconds. Default: 600 seconds -d delay Minimum delay between replication runs in rolling replication mode. Larger values provide better efficiency as transactions can be merged. Smaller values mean that the replica system is more up to date and that you don't end up with large blocks of replication transactions as a single group. Default: 3 seconds. -r Rolling (repeat) replication mode. Pick up a list of actions recorded by the lmtpd(8), imapd(8), popd(8) and nntpd(8) daemons from the file specified in sync_log_file. Repeat until sync_shutdwon_file appears. -n Use the named channel for rolling replication mode. If multiple channels are specified in sync_log_channels then use one of them. This option is probably best combined with -S to connect to a different server with each channel. -u User mode. Remaining arguments are list of users who should be replicated. -m Mailbox mode. Remaining arguments are list of mailboxes which should be replicated. -s Sieve mode. Remaining arguments are list of users whose Sieve files should be replicated. Principally used for debugging purposes: not exposed to sync_client(8). FILES
/etc/imapd.conf SEE ALSO
sync_server(8) AUTHORS
David Carter (dpc22@cam.ac.uk), Ken Murchison (ken@oceana.com) CMU
Project Cyrus SYNC_CLIENT(8)
All times are GMT -4. The time now is 09:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy