[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: replication on 2.4.13



Hi.

This problem can be solved increasing the syncprov-sessionlog value.
If syncprov-sessionlog is disable, none delete operation is replicate to master B.

From Administrator's Guide:

"In the present phase, the provider sends the consumer the entries updated within the search scope since the last synchronization. The provider sends all requested attributes, be they changed or not, of the updated entries. For each unchanged entry which remains in the scope, the provider sends a present message consisting only of the name of the entry and the synchronization control representing state present. The present message does not contain any attributes of the entry. After the consumer receives all update and present entries, it can reliably determine the new consumer copy by adding the entries added to the provider, by replacing the entries modified at the provider, and by deleting entries in the consumer copy which have not been updated nor specified as being present at the provider."

Why is this not happening in MultiMaster configuration ?

Best Regards,

On Tue, Jan 6, 2009 at 6:58 PM, jakjr <joao.alfredo@gmail.com> wrote:
Hello,

I'm testing a multimaster config on openldap 2.4.13.

I have 2 servers. Adds and Modifies are ok on both.

But, when I deleted 300 entries, with server B down and this server goes up again, those entries deleted from server A are no replicated. Server B still keeping those entries.

This is a bug or a config error.

This is my config:

ServerID XXX

syncrepl rid=001
  provider=ldap://<IP>
  type=refreshAndPersist
  retry="5 5 10 +"
  searchbase="dc=br"
  bindmethod=simple
  binddn="cn=admin,dc=br"
  credentials=**
  schemachecking=off

mirrormode on

overlay syncprov
syncprov-checkpoint 100 1
syncprov-reloadhint TRUE
syncprov-sessionlog 100

Thanks