OK, what do you mean by "index is kicked off"? You mean starting Solr
or actually adding a document to a running Solr?
If the latter, you're probably looking for something like this:
Feb 9, 2012 10:34:26 AM
org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {add=[eoe32]} 0 6
The important bits are solr.update.processor and the add=blahblah bit
where the stuff after the =
will be a list of <uniqueKey>s for the document(s) added.
However, this will be somewhat fragile, the format of the logged messages is not
guaranteed in future versions.
Although this is happening, I think, after the doc has been added to
the index, so it
may be too late for your problem.
Best
Erick
On Wed, Feb 8, 2012 at 3:13 PM, Hoffman, Chase <hoffm...@advisory.com> wrote:
> Please forgive me if this is a dumb question. I've never dealt with SOLR
> before, and I'm being asked to determine from the logs when a SOLR index is
> kicked off (it is a Windows server). The TOMCAT service runs continually, so
> no love there. In parsing the logs, I think
> "org.apache.solr.core.SolrResourceLoader <init>" is the indicator, since
> "org.apache.solr.core.SolrCore execute" seems to occur even when I know an
> index has not been started.
>
> Any advice you could give me would be wonderful.
>
> Best,
>
> --Chase
>
> Chase Hoffman
> Infrastructure Systems Administrator, Performance Technologies
> The Advisory Board Company
> 512-681-2190 direct | 512-609-1150 fax
> hoffm...@advisory.com<mailto:hoffm...@advisory.com> |
> www.advisory.com<http://www.advisory.com>
>
> Don't miss out-log in now
> Unlock thousands of members-only tools, events, best practices, and more at
> www.advisory.com.
> Get
> started<http://www.advisory.com/reasons-to-log-in-now/?WT.mc_id=eMail|SignatureLine|Other|ABC|Login+8+Reasons|Nov212011>
