Solr report - how to interpret
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2012 03:16 AM
If I run https://servername:8443/solr/admin/cores?action=REPORT I get a report like
"Count of transactions in the index but not the DB" 1478 - Why can this be, and is it a sign of serious error?
"First transaction in the index but not the DB" 716 - This I guess is complementary information to the above.
These are the ones I need to understand for the moment, but it could be useful if each post and what to make of them is added to http://wiki.alfresco.com/wiki/Alfresco_And_SOLR#Checking_the_status_of_the_SOLR_index (I could help with that if I had the answer).
<response><lst name="responseHeader"><int name="status">0</int><int name="QTime">185419</int></lst><lst name="report"><lst name="alfresco"><long name="DB transaction count">13740</long><long name="DB acl transaction count">191</long><long name="Count of duplicated transactions in the index">0</long><long name="Count of duplicated acl transactions in the index">0</long><long name="Count of transactions in the index but not the DB">1478</long><long name="First transaction in the index but not the DB">716</long><long name="Count of acl transactions in the index but not the DB">0</long><long name="Count of missing transactions from the Index">0</long><long name="Count of missing acl transactions from the Index">0</long><long name="Index transaction count">15218</long><long name="Index acl transaction count">191</long><long name="Index unique transaction count">15218</long><long name="Index unique acl transaction count">191</long><long name="Index leaf count">12292</long><long name="Count of duplicate leaves in the index">0</long><long name="Last index commit time">1329291823222</long><str name="Last Index commit date">2012-02-15T08:43:43</str><long name="Last TX id before holes">6571433</long></lst><lst name="archive"><long name="DB transaction count">13740</long><long name="DB acl transaction count">191</long><long name="Count of duplicated transactions in the index">0</long><long name="Count of duplicated acl transactions in the index">0</long><long name="Count of transactions in the index but not the DB">1478</long><long name="First transaction in the index but not the DB">716</long><long name="Count of acl transactions in the index but not the DB">0</long><long name="Count of missing transactions from the Index">0</long><long name="Count of missing acl transactions from the Index">0</long><long name="Index transaction count">15218</long><long name="Index acl transaction count">191</long><long name="Index unique transaction count">15218</long><long name="Index unique acl transaction count">191</long><long name="Index leaf count">5610</long><long name="Count of duplicate leaves in the index">0</long><long name="Last index commit time">1329291823222</long><str name="Last Index commit date">2012-02-15T08:43:43</str><long name="Last TX id before holes">6571433</long></lst></lst></response>
I need some help here on how to interpret some data in the report"Count of transactions in the index but not the DB" 1478 - Why can this be, and is it a sign of serious error?
"First transaction in the index but not the DB" 716 - This I guess is complementary information to the above.
These are the ones I need to understand for the moment, but it could be useful if each post and what to make of them is added to http://wiki.alfresco.com/wiki/Alfresco_And_SOLR#Checking_the_status_of_the_SOLR_index (I could help with that if I had the answer).
Labels:
- Labels:
-
Archive
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2012 09:18 AM
Hi
I have added the extra information to the Wiki.
"Count of transactions in the index but not the DB" 1478
"First transaction in the index but not the DB" 716
This can mean your index does not match the DB (which we should check for at start up using the first TXN)
Emtpy transactions can be purged from the repo (and still remain in the index) with no related docs.
This is no issue.
You can check the doc count on the DB or directly against the index using INTXID=716
It is also possible this transaction has been skipped due to a known bug (there are a couple)
Using the FIX option will sort this out.
Normally the tracker will stop and retry rather then skip past and never return.
Again this may change.
At some point we will add TX purging to match the DB and in teh report check for "real" problems.
Andy
I have added the extra information to the Wiki.
"Count of transactions in the index but not the DB" 1478
"First transaction in the index but not the DB" 716
This can mean your index does not match the DB (which we should check for at start up using the first TXN)
Emtpy transactions can be purged from the repo (and still remain in the index) with no related docs.
This is no issue.
You can check the doc count on the DB or directly against the index using INTXID=716
It is also possible this transaction has been skipped due to a known bug (there are a couple)
Using the FIX option will sort this out.
Normally the tracker will stop and retry rather then skip past and never return.
Again this may change.
At some point we will add TX purging to match the DB and in teh report check for "real" problems.
Andy
