On 3/8/2012 7:02 AM, stetogias wrote:
Hi,
Trying to understand the update handler statistics
so I have this:
commits : 2824
autocommit maxDocs : 1
autocommit maxTime : 1000ms
autocommits : 41
optimizes : 822
rollbacks : 0
expungeDeletes : 0
docsPending : 0
adds : 0
deletesById : 0
deletesByQuery : 0
errors : 0
cumulative_adds : 17457
cumulative_deletesById : 1959
cumulative_deletesByQuery : 0
cumulative_errors : 0
my problem is with the cumulative part.
If for instance I am doing a commit after each add and delete operation then
the sum of cumulative_adds plus
cumulative_deletes plus cumulative_errors should much the commit number.
is that right?
And another question, these stats are since SOLR instance startup or since
update handler startup, these
can differ as far as I understand...
and from this part:
docsPending : 0
adds : 0
deletesById : 0
deletesByQuery : 0
errors : 0
I understand that if I had docsPending I should have adds(pending)
deletes*(pending) but how could I have errors...
I'm fairly sure that adds and deletes refer to the number of documents
added or deleted. You can have many documents added and/or deleted for
each commit. I would not expect the sums to match, unless you are
adding or deleting only one document at a time and doing a commit after
every one. I hope you're not doing that, unless you're using trunk with
the near-realtime feature and doing soft commits, with which I have no
experience. Normally doing a commit after every document would be too
much of a load for good performance, unless there is a relatively long
time period between each add or delete.
Your question about errors - that probably tracks the number of times
that the update handler returned an error response, though I don't
really know. If I'm right, then that number, like commits, has little
to do with the number of documents.
Thanks,
Shawn
