Bug 1346315

Summary: nsslapd-maxbersize should be ignored in replication
Product: Red Hat Directory Server Reporter: Petr Bokoc <pbokoc>
Component: Doc-config-command-file-referenceAssignee: Marc Muehlfeld <mmuehlfe>
Status: CLOSED CURRENTRELEASE QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0CC: mmuehlfe, nhosoi, rhel-docs
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: 1223510 Environment:
Last Closed: 2016-12-19 08:31:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1223510    
Bug Blocks:    

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.