Bug 1219208

Followed these steps to verify this bug:
1. Configured 2 way MMR setup.
2. Stopped M2 and ran cleanallruv tasks in a while loop.
val=1 ; while [ $val -lt 70 ];do ./cleanallruv.pl -D "cn=Directory Manager" -w Secret123 -b "dc=passsync,dc=com" -r 1232 ; val="`expr $val + 1`"; sleep 1 ; done
3. More than 64 concurrent Cleanallruv tasks created.
ldapsearch -LLL -x -p 1189 -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=cleanallruv, cn=tasks, cn=config" |grep -i "dn: cn=cleanallruv_2015*" |wc -l
69
4. Then I tried creating more than 64 concurrent tasks for different rids.
val=1 ; while [ $val -lt 70 ];do ./cleanallruv.pl -D "cn=Directory Manager" -w Secret123 -b "dc=passsync,dc=com" -r 12${val} ; val="`expr $val + 1`"; sleep 1 ; done

5. Even with different Replica Ids, more than 64 concurrent cleanallruv tasks were created.

Is this something expected?

(In reply to Sankar Ramalingam from comment #2)
> Followed these steps to verify this bug:
> 1. Configured 2 way MMR setup.
> 2. Stopped M2 and ran cleanallruv tasks in a while loop.
> val=1 ; while [ $val -lt 70 ];do ./cleanallruv.pl -D "cn=Directory Manager"
> -w Secret123 -b "dc=passsync,dc=com" -r 1232 ; val="`expr $val + 1`"; sleep
> 1 ; done
> 3. More than 64 concurrent Cleanallruv tasks created.
> ldapsearch -LLL -x -p 1189 -h localhost -D "cn=Directory Manager" -w
> Secret123 -b "cn=cleanallruv, cn=tasks, cn=config" |grep -i "dn:
> cn=cleanallruv_2015*" |wc -l
> 69
> 4. Then I tried creating more than 64 concurrent tasks for different rids.
> val=1 ; while [ $val -lt 70 ];do ./cleanallruv.pl -D "cn=Directory Manager"
> -w Secret123 -b "dc=passsync,dc=com" -r 12${val} ; val="`expr $val + 1`";
> sleep 1 ; done
> 
> 5. Even with different Replica Ids, more than 64 concurrent cleanallruv
> tasks were created.
> 
> Is this something expected?

This is definitely a problem, nice catch!  We were incorrectly checking the number of tasks that were at later stage of cleaning.  I will start working on the fix (it is trivial).

Thanks Mark!. Changing the status of the bug to Assigned.

Additional Info:
[root@hp-dl380pgen8-02-vm-3 ~]# rpm -qa |grep -i 389-ds-base
389-ds-base-libs-1.2.11.15-56.el6.x86_64
389-ds-base-debuginfo-1.2.11.15-56.el6.x86_64
389-ds-base-1.2.11.15-56.el6.x86_64

Fixed upstream

The verification steps need to be adjusted.  Use this search instead to detect active tasks:

ldapsearch -LLL -x -p 1189 -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=cleanallruv, cn=tasks, cn=config" -xLLL nstaskstatus=* | grep "^dn: " | wc -l

Created more than 64 concurrent cleanallruv tasks as mentioned in comment #3. Then, checked the cleanallruv tasks created by running the following command.

[root@qe-blade-01 ~]# ldapsearch -LLL -x -p 1189 -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=cleanallruv, cn=tasks, cn=config" -xLLL nstaskstatus=* | grep "^dn: " | wc -l
64

The number of cleanallruv tasks was limited to 64. Hence, marking the bug as verified.

Build tested:
[root@qe-blade-01 ~]# rpm -qa|grep -i 389-ds-base
389-ds-base-1.2.11.15-60.el6.x86_64
389-ds-base-libs-1.2.11.15-60.el6.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1326.html