Description of problem: During the verification of Winsync range retrieval RFE we came accross this problem. When a group (any entry) witm a lot of multi valued attribute values, such as members of a group is being synchronized in full replica refresh/winsync agreement initialization, only 5000 values are synchronized. No changes are fetched during the checks via incremental upgrade. After the second refresh of a synchronization agreement in question, all the values are fetched, even if there is more than 5000 of them. Changing value of lDAPAdminLimits: MaxResultSetSize on Active Directory, suggested by Noriko, hasn't had any visible effect on the issue. Windows Server 2008 R2 Enterprise with latest available updates How reproducible: always Steps to Reproduce: 1. Create more than 5000 users and a group containing them on Active Directory 2. Create a windows synchronization agreement on a Directory Server instance. 3. Initialize the synchronization agreement. (nsds5beginReplicaRefresh: start) Actual results: All of the users and group are synchronized. The group contains only 5000 members, though. Expected results: The group is synchronized completely with all of its members. Additional info:
I could not reproduce the problem.
git patch file (master) 0001-Ticket-48010-winsync-range-retrieval-gets-only-5000-.patch
Note: the total update scenario with a group entry having 10000 members on AD was tested with valgrind and no leak was reported.
Reviewed by Rich (Thank you!) Researched and tested by Viktor (Thank you!)
Pushed to master: 684f8c5..c6b211f master -> master commit c6b211f
Pushed to 389-ds-base-1.3.4: 6d43988..d9af22e 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit d9af22e
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.4.2
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1341
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.