Bug 1346315 - nsslapd-maxbersize should be ignored in replication
Summary: nsslapd-maxbersize should be ignored in replication
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-config-command-file-reference
Version: 10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1223510
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-14 14:09 UTC by Petr Bokoc
Modified: 2016-12-19 08:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The configuration parameter nsslapd-maxbersize defines the maximum size in bytes allowed for an incoming message. The same restriction was applied to the replication and it caused the replication fail when a larger size of entry was replicated. Fix: The replication operation does not need be restricted, thus the size limit has been eliminated. Result: The replication does not fail with a large entry any more.
Clone Of: 1223510
Environment:
Last Closed: 2016-12-19 08:31:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Petr Bokoc 2016-06-14 14:10:15 UTC 
We might need to mention this at least in the attribute description in  ⁠3.1.1.88. nsslapd-maxbersize (Maximum Message Size) in the Configuration, Command and File Reference.
Comment 4 Marc Muehlfeld 2016-12-19 08:31:05 UTC 
The update is now available on the Customer Portal.
Note You need to log in before you can comment on or make changes to this bug.