[Fedora-directory-users] 'Server Side Sorting' in many entries Problem....
Richard Megginson
rmeggins at redhat.com
Tue Mar 13 13:59:13 UTC 2007
Yasuhiro Hiraishi wrote:
> Hello,
>
>
>> You mean, have the client set the size limit? Yes, but the client
>> cannot set the maximum to be higher than the maximum configured on the
>> server side. The sizelimit is part of the LDAP Search Request.
>>
>
> Yes, I mean, have the client set size limit.
>
>
>> What are your server and client side sizelimit settings?
>>
>
> I set "1000" as the client size limit and
> set "2147483647" as the server side size limit in those parameters:
>
> ・ "Perfomance tab" -> "sizelimit"
> ・ "Database Link Setting" -> "Default Creation Parameter tab" ->
> "sizelimit"
> ・ "Database Setting" -> "LDBM-Plugin Setting tab" -> "Look-through limit"
>
> I'm not sure which parameters are actually the server side size limit.
>
All of these are server side limits.
What is your client?
>
> Thank you.
>
> On Tue, 06 Mar 2007 20:40:33 -0700
> Richard Megginson <rmeggins at redhat.com> wrote:
>
>
>> Yasuhiro Hiraishi wrote:
>>
>>> Hello..
>>>
>>>
>>>
>>>>> Bellow, I done
>>>>> ------------------------------------------
>>>>> 1. Install Fedora Directory Service.
>>>>> 2. Change look-through limit in Database Setting to 2147483647 from the Server Console.
>>>>> 3. Creating Presence and Substring Indexes of 'uid' from the Server Console
>>>>>
>>>>>
>>>>>
>>>> Was there not already a presence index for uid?
>>>>
>>>>
>>> Sorry. I had a mistake. There was already a presence index.
>>>
>>>
>>>
>>>> This may also be a problem with the search sizelimit.
>>>>
>>>>
>>> What dose 'sizelimit' mean?
>>> Do you mean configulation which limits how many entirues are retuned from a FDS server?
>>>
>>>
>> Yes.
>>
>>> Is it possible to use 'Server Side Sorting' with sizelimit at a client side?
>>>
>>>
>> You mean, have the client set the size limit? Yes, but the client
>> cannot set the maximum to be higher than the maximum configured on the
>> server side. The sizelimit is part of the LDAP Search Request.
>>
>>> I want to know why 'Server Side Sorting' is working in 4000 entries
>>> but not working in rather than 5000 entries,
>>> In those of situations 'sizelimit' is 1000.
>>>
>>>
>> What are your server and client side sizelimit settings?
>>
>>> I will show you the access log when success.
>>> --<SORT OK>------------------------
>>> [01/Mar/2007:14:05:24 +0900] conn=93 fd=68 slot=68 connection from 127.0.0.1 to 127.0.0.1
>>> [01/Mar/2007:14:05:24 +0900] conn=93 op=0 BIND dn="" method=128 version=3
>>> [01/Mar/2007:14:05:24 +0900] conn=93 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn=""
>>> [01/Mar/2007:14:05:24 +0900] conn=93 op=1 SRCH base="ou=Users,o=Section,o=Company" scope=1 filter="(uid=*)" attrs=ALL
>>> [01/Mar/2007:14:05:24 +0900] conn=93 op=1 SORT uid (4000)
>>> [01/Mar/2007:14:05:26 +0900] conn=93 op=1 RESULT err=4 tag=101 nentries=1000 etime=2 notes=U
>>> [01/Mar/2007:14:05:26 +0900] conn=93 op=2 UNBIND
>>> [01/Mar/2007:14:05:26 +0900] conn=93 op=2 fd=68 closed - U1
>>> ---
>>>
>>> Do you know how to use 'Server Side Sorting' in any amount of entriyes with client side sizelimit?
>>>
>>> Thank you.
>>>
>>> On Mon, 05 Mar 2007 10:28:34 -0700
>>> Richard Megginson <rmeggins at redhat.com> wrote:
>>>
>>>
>>>
>>>> Yasuhiro Hiraishi wrote:
>>>>
>>>>
>>>>> Hello.
>>>>>
>>>>> I am planning to use the Fedora Directory Server
>>>>> in Redhat Linux ES4.0 to do 'Server Side Sorting'.
>>>>> The system processed around 4000 entries successfully.
>>>>> However, when the system tried processing more than 5000 entries,
>>>>> it returned an error such as 'LDAP_UNWILLING_TO_PERFORM'.
>>>>>
>>>>> Does anyone know how to fix this problem?
>>>>>
>>>>> Just in case, Ishow you the error logs below...
>>>>>
>>>>> --<Error Log>------------------------
>>>>> [01/Mar/2007:14:07:15 +0900] conn=96 fd=68 slot=68 connection from 127.0.0.1 to 127.0.0.1
>>>>> [01/Mar/2007:14:07:15 +0900] conn=96 op=0 BIND dn="" method=128 version=3
>>>>> [01/Mar/2007:14:07:15 +0900] conn=96 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn=""
>>>>> [01/Mar/2007:14:07:15 +0900] conn=96 op=1 SRCH base="ou=Users,o=Section,o=Company" scope=1 filter="(uid=*)" attrs=ALL
>>>>> [01/Mar/2007:14:07:15 +0900] conn=96 op=1 SORT uid (*)
>>>>> [01/Mar/2007:14:07:16 +0900] conn=96 op=1 RESULT err=4 tag=101 nentries=1000 etime=1 notes=U
>>>>> [01/Mar/2007:14:07:17 +0900] conn=96 op=2 UNBIND
>>>>> [01/Mar/2007:14:07:17 +0
>>>>> -----
>>>>>
>>>>> Bellow, I done
>>>>> ------------------------------------------
>>>>> 1. Install Fedora Directory Service.
>>>>> 2. Change look-through limit in Database Setting to 2147483647 from the Server Console.
>>>>> 3. Creating Presence and Substring Indexes of 'uid' from the Server Console
>>>>>
>>>>>
>>>>>
>>>> Was there not already a presence index for uid?
>>>>
>>>> This may also be a problem with the search sizelimit.
>>>>
>>>>
>>>>> 4. I start entry ....
>>>>> --
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>> --
>>>>> Fedora-directory-users mailing list
>>>>> Fedora-directory-users at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>>>>
>>>>>
>>>>>
>>> --
>>> Fedora-directory-users mailing list
>>> Fedora-directory-users at redhat.com
>>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>>
>>>
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3245 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-directory-users/attachments/20070313/b4160f1e/attachment.bin>
More information about the Fedora-directory-users
mailing list