On 3/5/2016 5:33 AM, Steven White wrote:
> 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 va
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?
Ste
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 "
HI folks,
I am analyzing a performance issue with Solr during indexing. My
simplefiled psedue code looks like so
while (more-items) {
for (int i = 0; i < 100; i++) {
docs.add(doc);
}
UpdateResponse resp = solrConn.add(docs, 1); // <== yes, using "1"
is bad
