Paul Lemoine wrote:
I have tested a bigger value for the idlistscanlimit (10*4000 = 40000) and the search problem disappeared.No, there is a rule between idlistscanlimit and how many entries you expect to match a single search. So if you are planning to do searches like (cn=*e*) you should have a very large idlistscanlimit.Thanks you for everyoneNow I wonder what could be its value for a directory which intends to reach 3 000 000 inetOrgPerson ?Is there a rule between idlistscanlimit and the number of entries ?
Thanks you Regards Paul. Rich Megginson a écrit :Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe. This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.Paul Lemoine wrote:How many entries match cn=smith*? uid=25698*? I think the problem is the idlistscanlimit as mentioned by another poster.Hi, I have a search problem with Fedora DS 1.1.3.My directory has an extended schema on the objectClass "inetOrgPerson". It contains 350000 inetOrgPerson objects. When I proceed a search with that kind of filter (cn=smith*) or (uid=25698*) the response comes 1 minute later with a error code 11.Indexes on cn and uid attribute are on equality, presence and substring. I have recreated (plus reindexed) this attribute. I put the look-through-limit to infinity though I don't have the errror code 11 anymore but I have to wait a very long time the response. In the log, I found "etime=77 notes=U" which means that the search does not use the indexes.I have done the same requests with a "native" schema : it works perfectly. So, it is my extended schema which causes the problem.Can the Fedora DS (or 389 DS) deal with extended schema ?Does anybody met this problem ? Is there a solution for forcing FDS to use the indexes ?Regards Thanks you Paul.Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe. This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users------------------------------------------------------------------------ -- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
<<attachment: smime.p7s>>
-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
