Error: The search application requested too many results.
Anyone knows what this error means?
The search application requested too many results. Index: %1 Requested number of results: %2 Maximum number of results: %3
Forum Discussion
5 Replies
Hiya,
Its not something I've really seen occur...presuming this is either an indexserver or w3wp error, it would be useful if we had a dtrace snippet to work with
We've developed a third-party application for Enterprise Vault 2007 and I'm getting the exact same error.
We request batches of 100 items at once to the Search Application. However, in my DTrace logs (IndexServer), it seems that the server gradually builds a batch up to 700 items! The error from the EV API seems to occur at the exact same time we reach 700 items :
1459 10:52:25.938 [5332] (IndexServer) <4964> EV:M CAltaVistaSearch::NonChunkedSearch|Search Complete; returning 100 results from a total of 154656|Results discarded: 0|Memory: 5MB
...
3174 10:52:54.907 [5332] (IndexServer) <4964> EV:M CAltaVistaSearch::NonChunkedSearch|Search Complete; returning 200 results from a total of 154656|Results discarded: 0|Memory: 5MB
...
15175 10:55:29.468 [5332] (IndexServer) <4964> EV:M CAltaVistaSearch::NonChunkedSearch|Search Complete; returning 700 results from a total of 154656|Results discarded: 0|Memory: 6MBIn another test environment, my IndexServer logs always show batches of 100 items or less :
Search Complete; returning 100 results from a total of XXXXX
Any ideas?
Searches in DA,
We have seen something simular when running DA searches.
If this error is showing up in DA do a test with the below settings
IN DA click on the System Configuration option on the right side of the screen
When the sys config page opens at the top of the screen you will see in the greay banner System Configuration
Hold down the CTRL key and click on the workd System Configuration
This will allow you to see the hidden settings
Search Chunk Size and set it to 1000
Find MAX Number of Threads per index and set this to 1
After thses settings have been applied you will need to restart the accelerator service.
In our case the issue was the the indexserver.exe was causing this issue. There is a fix for it but it will depend on what version of DA and EV you are running
Do this test and let me know the outcome.
Also am I right in saying that this happens with large searches but not when you run small searches?
- @Darc Backer Are you using the Search API? Cheers Michel
- @MichelZ: Yes, we perform our queries with the Search() function on the IndexSearch2Class object. It is available through the Search API.
@Scanner001 : as I understand it, by "DA" you mean "Discovery Accelerator". We don't use it.
As I said, we specifify a constant batch size (always 100 items), so I don't think it's normal that the server tries to send back 700 items.
The above error doesn't seem to be documented anywhere :
The search application requested too many results. Index: %1 Requested number of results: %2 Maximum number of results: %3
Any ideas?
