Hi Howard, Le mercredi 27 octobre 2010 15:03:36, Howard Chu a =E9crit : > [email protected] wrote: > > Full_Name: Sebastien Bahloul > > Version: HEAD > > OS: Linux RHEL 5 > > URL: > > Submission from: (NULL) (109.197.176.10) > >=20 > >=20 > > Hi, > >=20 > > I think there is a bug / limitation inside VLV implementation : it can > > not handle multiple search operation on a single connection. The first > > operation succeeds and next operations fail with the following message : > >=20 > > LDAP: error code 51 - Other sort requests already in progress > >=20 > > But I think this issue is more global. This implementation seems to be > > able to only handle a single VLV context per connection. >=20 > Correct, that is by design. >=20 > > If I am right, this is related with the indexing method of sort_conns > > structure which seems to be based only on the connection id. I suggest > > to implement a double indexing array by connection id / VLV context id. >=20 > I have no interest in extending this. It would require much more overhead > to protect the slapd from getting overloaded by too many such requests.
In fact my suggestion was a question : I would like to contribute a patch t= o=20 add support for this way of using VLV. Is this feature extension as a doubl= e=20 indexed array an acceptable implementation from your point of vue ? To avoi= d=20 encountering such performance issues, I would add a new sssvlv parameter th= at=20 would authorize by default only a single VLV search request per connection. Regards, =2D-=20 Sebastien Bahloul @: [email protected]
