|
Benjamin Plaquevent
|
Tuesday 11 March 2008 3:13:39 am
Hi, I currently use eZFind 1.0.0beta2 on eZPublish 4.0. I have a strange eZFind indexer script behaviour : It starts indexing and stops at 36% without any error message... (when run without special debug / loging params) Indexer script terminates with following output:
Creating a new thread: 2645
.................................................. 34.19%
...................................................................... 35.17%
...................................................................... 36.15%
..........Process finished: 2643
Process finished: 2645
Optimizing. Please wait ...
Indexing took 242.269028902 secs ( average: 29.5745602831 objects/sec )
Finished updating the search index.
Solr server output:
INFO: Closing Searcher@fbf51d main
filterCache{lookups=0,hits=0,hitratio=0.00,inserts=0,evictions=0,size=0,cumulative_lookups=0,cumulative_hits=0,cumulative_hitratio=0.00,cumulative_inserts=0,cumulative_evictions=0}
queryResultCache{lookups=0,hits=0,hitratio=0.00,inserts=0,evictions=0,size=0,cumulative_lookups=0,cumulative_hits=0,cumulative_hitratio=0.00,cumulative_inserts=0,cumulative_evictions=0}
documentCache{lookups=0,hits=0,hitratio=0.00,inserts=0,evictions=0,size=0,cumulative_lookups=0,cumulative_hits=0,cumulative_hitratio=0.00,cumulative_inserts=0,cumulative_evictions=0}
eZPublish error log:
[ Mar 11 2008 11:07:02 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: BEGIN WORK
[ Mar 11 2008 11:07:02 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: COMMIT
[ Mar 11 2008 11:07:02 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: DELETE FROM ezsession WHERE session_key='d7bddb3cb470f958bc95d88d835477fc'
[ Mar 11 2008 11:07:08 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: BEGIN WORK
[ Mar 11 2008 11:07:08 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: COMMIT
[ Mar 11 2008 11:07:08 ] [] eZMySQLDB:
Query error: MySQL server has gone away. Query: DELETE FROM ezsession WHERE session_key='d7bddb3cb470f958bc95d88d835477fc'
So it appears that there is a mysql connexion error but I can't figure why.
I try to index ~20.000 ezpublish objects.
Trying to index few basic objects works normaly. Does anyone can help please?
Benjamin Plaquevent
Project Manager
Smile
|
|
Heath
|
Tuesday 11 March 2008 5:17:51 am
Ahh! I had heard this would become a problem with eZ Find ... We have seen this design flaw before in the php indexing cronjob/scripts in the past releases. We created an alternative solution which has been used by several customers with great success. http://projects.ez.no/updatesearchindex Now eZ Find appears at a glance to offer the same problem. I think the solution for you might be along similar lines. In the end the problem logic surrounds how it indexes sites with any more than a small amount of content object content. Our solution provides for an incremental indexing solution which might be able to be adapted to meet your needs with eZ find. IE: use the logic/design pattern not actual code of updatesearchindex extension.
Cheers,
Heath
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|
