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, but ...
        docs.clear();
    }

Now looking at Solr's log, I want to understand the events that generates:

    solrConn.add(docs, 1);

Yes, I know using "1" is a bad practice, but that's not what I'm after.  I
set this to "1" so I can understand:

1) what are the end-to-end operation Solr does to finish this action, and
2) how long does this call blocks before it returns.

Looking at the logs, I see this:

    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?

Thanks in advanced.

Steve

Reply via email to