On 5/5/2014 8:55 AM, Graham Leggett wrote:
One of the objects being replicated is a large group containing about 21000 uniqueMembers. When it comes to replicate this object, the replication pauses for about 6 seconds or so, and at that point it times out, responding with the following misleading error message:
[05/May/2014:15:33:36 +0100] NSMMReplicationPlugin - agmt="cn=Agreement serverc.example.com" (serverc:636): Failed to send extended operation: LDAP error -1 (Can't contact LDAP server)
serverc is in Johannesburg, on a far slower connection than servera in DFW and serverb in London. It appears there is some kind of timeout that kicks in and causes the replication to suddenly be abandoned without warning.
Does anyone know what timeout is used during replication and how you set this timeout?
Not ottomh but this will be covered in the documentation :
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/8.2/html/Configuration_and_Command-Line_Tool_Reference/Core_Server_Configuration_Reference.html#cnconfig
I'd be astonished if the default timeout is anything close to as short
as 6 seconds though.
The setting might be "nsslapd-outbound-ldap-io-timeout", but the docs
say the default is 5 minutes.
fwiw in more than 15 years working on the DS, I can't recall ever
hearing of a problem caused by the timeout on replication connections
being too _short_, but I suppose there's a first time for everything...
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
