----- "Adrien Futschik" adrien.futschik@atosorigin.com wrote:
I am testing Multi-master replication with two masters.
If I stop one of them and don't restart it before the end of retry interval, the replication process doesn't work anymore. (looks like it is stopped).
exemple :
- M1 & M2 are synchronised.
- stop M2
- add entries to M1
- wait for retry to fail (retry="5 5 300 5")
- restart M2
- previously added entries to M1 are replicated to M2
- modifying M2 (attributes) are not replicated to M1
It look like M1 -> M2 : OK and M2 -> M1 : broken
Is there a way to restart replication after configured retry are over ? The solution I found was to restart M1. After that everything seems to work fine.
I could set up retry so that the number of retry is very hight, but I was wondering if there was a way to restart synchronisation online.
"If an error occurs during replication, the consumer will attempt to reconnect according to the retry parameter which is a list of the <retry interval> and <# of retries> pairs. For example, retry="60 10 300 3" lets the consumer retry every 60 seconds for the first 10 times and then retry every 300 seconds for the next 3 times before stop retrying. The '+' in <# of retries> means indefinite number of retries until success. If no retry was specified, by default syncrepl retries every hour forever."
Why not just change it to retry="60 +" ?
Le mercredi 18 février 2009 16:27:43, Gavin Henry a écrit :
----- "Adrien Futschik" adrien.futschik@atosorigin.com wrote:
I am testing Multi-master replication with two masters.
If I stop one of them and don't restart it before the end of retry interval, the replication process doesn't work anymore. (looks like it is stopped).
exemple :
- M1 & M2 are synchronised.
- stop M2
- add entries to M1
- wait for retry to fail (retry="5 5 300 5")
- restart M2
- previously added entries to M1 are replicated to M2
- modifying M2 (attributes) are not replicated to M1
It look like M1 -> M2 : OK and M2 -> M1 : broken
Is there a way to restart replication after configured retry are over ? The solution I found was to restart M1. After that everything seems to work fine.
I could set up retry so that the number of retry is very hight, but I was wondering if there was a way to restart synchronisation online.
"If an error occurs during replication, the consumer will attempt to reconnect according to the retry parameter which is a list of the <retry interval> and <# of retries> pairs. For example, retry="60 10 300 3" lets the consumer retry every 60 seconds for the first 10 times and then retry every 300 seconds for the next 3 times before stop retrying. The '+' in <# of retries> means indefinite number of retries until success. If no retry was specified, by default syncrepl retries every hour forever."
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry ends. A command like "start slave" for mysql. ...
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry ends. A command like "start slave" for mysql. ...
A restart of slapd will trigger a scan etc. or start the consumer it with the -c option.
Thanks.
----- "Gavin Henry" ghenry@suretecsystems.com wrote:
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry ends. A command like "start slave" for mysql. ...
A restart of slapd will trigger a scan etc. or start the consumer it with the -c option.
Thanks.
In fact, just search the list archives for an example, as this is always asked.
Gavin.
Gavin Henry wrote:
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry ends. A command like "start slave" for mysql. ...
A restart of slapd will trigger a scan etc. or start the consumer it with the -c option.
Server restarts are a pretty primitive solution. If you're using cn=config, just ldapmodify the entry and replace the olcSyncrepl line (with itself).
----- "Howard Chu" hyc@symas.com wrote:
Gavin Henry wrote:
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry
ends.
A command like "start slave" for mysql. ...
A restart of slapd will trigger a scan etc. or start the consumer it
with the -c option.
Server restarts are a pretty primitive solution. If you're using cn=config, just ldapmodify the entry and replace the olcSyncrepl line (with itself).
But if you haven't got cn=config setup yet (you should!) the primative way is needed ;-)
Gavin.
Le mercredi 18 février 2009 23:13:43, Gavin Henry a écrit :
----- "Howard Chu" hyc@symas.com wrote:
Gavin Henry wrote:
Why not just change it to retry="60 +" ?
I thought of that, I'll probably do something like that, but I was wondering if there was any other way to restart replication after retry
ends.
A command like "start slave" for mysql. ...
A restart of slapd will trigger a scan etc. or start the consumer it
with the -c option.
Server restarts are a pretty primitive solution. If you're using cn=config, just ldapmodify the entry and replace the olcSyncrepl line (with itself).
But if you haven't got cn=config setup yet (you should!) the primative way is needed ;-)
Gavin.
Thanks a lot to both of you Gavin & Howard !
In fact, I have cn=config setup. I started from test050-syncrepl-multimaster. I have cn=config replicating & data (bdb), I will try of replacing olcsyncrepl.
I allready tryed to change the retry parameter from one of the olcsyncrepl, but it didn't "trigered the replication". I'll try with the full replacement of the olcsyncrepl directive.
Adrien
openldap-technical@openldap.org
-
Adrien Futschik -
Gavin Henry -
Howard Chu