Thanks Shawn.
To make sure I get this right, I see two methods on UpdateResponse class,
is getElapsedTime the client time and getQTime Solr's time? If so, than
getElapsedTime is how long my call was blocked, right? And getQTime will
have the value of 1174 (per the log of my example), right?
Steve
On Sat, Mar 5, 2016 at 1:33 AM, Shawn Heisey <apa...@elyograg.org> wrote:
> On 3/4/2016 10:21 PM, Steven White wrote:
> > org.apache.solr.update.processor.LogUpdateProcessor; [test]
> > webapp=/solr path=/update params={wt=xml&version=2.2} {add=[5539783
> > (1527883353280217088), 5539867 (1527883353296994304), , ... (101 adds)]}
> 0
> > 1174
> >
> > What does this log tell me? Is "1174" the time (in milliseconds) it took
> > Solr to process those 101 documents? Does this mean "solrConn.add(docs,
> > 1)" was blocked for "1174" milliseconds?
>
> Yes, the QTime on the request was 1174 milliseconds. The UpdateResponse
> object has a getElapsedTime method that will tell you how long the
> request took from the client's point of view. Depending on which
> SolrClient implementation you used, as well as other performance
> factors, it may block for more or less time than what Solr reports in
> the QTime parameter.
>
> Thanks,
> Shawn
>
>
