When indexing additional nodes the return result is 200 nodes successfully indexed. but the number of nodes indexed does not increase.

I can tell it to reindex all the nodes and it works just fine up until 394629 nodes are indexed and then it keeps reporting more nodes being indexed but fails.

On tomcat6 http://solr:8080/searchapi/admin/file/?file=schema.xml

returns the following error:

XML Parsing Error: unclosed token
Location: http://solr:8080/searchapi/admin/file/?file=schema.xml
Line Number 164, Column 5:    <fieldType name="text" class="
----^

I have about 120k more nodes to index.

This seems to be the case with both the latest dev and the latest alpha.

Note: I selected miscellaneous because I don't know where the error is.

Comments

micheas’s picture

micheas commented
Component: Miscellaneous » Code

Something I did results in http://solr:8080/searchapi/admin/file/?file=schema.xml returning the correct file now, without complaints.

I am now getting the following error in the logs when I try and change the number of nodes indexed in one batch:

Maximum execution time of 120 seconds exceeded in /var/www/drupalmodules/search_api/search_api.module on line 1998

Could an upgrade have gone haywire and not fully modified all the needed database tables?

jonnyp’s picture

jonnyp commented

I had a similar isue when indexing over a million entities - basically I'd bumped up the number of entities per batch to process to 2000, without understanding how the queue system worked. Net result was the jobs were never sent to Solr as the queue process timed out, flagging entities as queued but never having enough time to send them to Solr. I had something like 300,000 unfinished jobs in my queue table!

I set the number of items per batch to 0 to clear this queue and indexing started again, but I still haven't found a sensible number for the items per batch

micheas’s picture

micheas commented

I "fixed" the problem with running
truncate queue
on the database.

if you have a database prefix you would run truncate prefix_queue. Well you get the idea.

OanaIlea’s picture

OanaIlea commented
Issue summary: View changes
Status: Active » Closed (outdated)

This issue was closed due to lack of activity over a long period of time. If the issue is still acute for you, feel free to reopen it and describe the current state.