#47957 Make ReplicaWaitForAsyncResults configurable
Closed: wontfix Opened by nhosoi.

Currently, supplier sleeps 1 second if it finds the response from consumer is not ready.

plugins/replication/repl5_inc_protocol.c
@@ -485,7 +486,7 @@ repl5_inc_waitfor_async_results(result_data *rd)
        }
        PR_Unlock(rd->lock);
        /* If not then sleep a bit */
        DS_Sleep(PR_SecondsToInterval(1));

The attached patch makes it configurable.


git patch file (389-ds-base-1.2.11)
configurable-WaitForAsyncResults.patch

Use INTEGER 1.3.6.1.4.1.1466.115.121.1.27 syntax for nsDS5ReplicaWaitForAsyncResults

In agmt_set_WaitForAsyncResults use slapi_entry_attr_get_int

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1171358

test script to cause lots of conflicts
reproducer.tar.gz

Reviewed by Rich (Thank you!!)

Pushed to master:
308c1bb..2802f36 master -> master
commit 2802f362395eac0bbbec99fef86ca27240da0d0f

Pushed to 389-ds-base-1.3.3:
748054f..06a5cc4 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 06a5cc4cf8732081489a443db2e782d78b53980f

Thanks for the nice test cases, Simon!

edaa28b..2c702c4 master -> master
commit 2c702c4f44512e8731c3d0a026cbc8838517345f
Author: Simon Pichugin spichugi@redhat.com
Date: Tue Oct 13 14:10:59 2015 +0200

46c4052..7ee822e 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit 7ee822e1a246d6d32a52dce5f7ad3ed9e491490d
Author: Simon Pichugin spichugi@redhat.com
Date: Tue Oct 13 14:10:59 2015 +0200

8081a91..339bbaf 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 339bbafbd8c35b944059395d2d2ff571a98b62ca
Author: Simon Pichugin spichugi@redhat.com
Date: Tue Oct 13 14:10:59 2015 +0200

Metadata Update from @rmeggins:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.3.9

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/1288

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata