Request time in query logs is exceeding the timeout value

Hi

We are using FAST ESP 5.3.SP5 for Enterprise Search in a client application. For one of the long search query request  the query logs show the response times too large number. I see two different response times in same query log as :

Below is just part of the log  where the RequestTime is 23387.6110 which is way too much than the SearchTime of 0.1710

ESP Search API Java, v 5.3.0.6" 23387.6110 0.1710 0.0000 0 &

 MANAGED(0, 0) STATS(0.1710, 0.0000, 0))]

1) Please let me know why the Total Request time is considerably more than SearchTime ? What is the exact meaning of TotalRequestTime as it is mentioned in the documents as total time taken to server request. Is the total request time is from the time the request originated from client (i.e java application) till the response returned ? or is the the total time taken by FAST ESP?

2) Will this kind of TotalRequestTime (23387.6110) will have any impact on the performance of FAST ESP?

3) What is the difference in the two parts of query_log  mentioned above which are part of same log message

Below are the timeout configurations on the system

etc\config_data\QRServer\webcluster\etc\qrserver\sources.xml :

    <timeout query="60" docsum="70"/>

etc\config_data\RTSearch\webcluster\fsearch.addon :

searchtimeout 60000
maxsocksilent 120

etc\config_data\RTSearch\webcluster\fdispatch.addon :

maxdocsumwait = 80
maxsearchwait = 70
maxsocksilent = 120

August 20th, 2015 5:37am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics