Skip to main content
Magento

Return to Question

edited tags
Link
Marius ♦
Marius ♦
  • 198.5k
  • 55
  • 424
  • 833
added 49 characters in body
Source Link
DSG
DSG
  • 423
  • 1
  • 3
  • 6

I'm using Solr with Enterprise Edition 1.13. When running a re-index on catalogsearch_fulltext from the command line about 15 minutes into the process the search on the site will start returning an error page with a MySQL error (1205: Lock wait timeout exceeded). Not long after that the indexer.php script dies. Has anyone else run into this problem? Seems like a bug in the core to me. We have not made any modifications associated with search. Running a re-index when using MySQL Fulltext for search works fine.

I'm using Solr with Enterprise Edition 1.13. When running a re-index on catalogsearch_fulltext from the command line about 15 minutes into the process the search on the site will start returning an error page with a MySQL error (1205: Lock wait timeout exceeded). Has anyone else run into this problem? Seems like a bug in the core to me. We have not made any modifications associated with search. Running a re-index when using MySQL Fulltext for search works fine.

I'm using Solr with Enterprise Edition 1.13. When running a re-index on catalogsearch_fulltext from the command line about 15 minutes into the process the search on the site will start returning an error page with a MySQL error (1205: Lock wait timeout exceeded). Not long after that the indexer.php script dies. Has anyone else run into this problem? Seems like a bug in the core to me. We have not made any modifications associated with search. Running a re-index when using MySQL Fulltext for search works fine.

Source Link
DSG
DSG
  • 423
  • 1
  • 3
  • 6

Using Solr search with Magento EE 1.13

I'm using Solr with Enterprise Edition 1.13. When running a re-index on catalogsearch_fulltext from the command line about 15 minutes into the process the search on the site will start returning an error page with a MySQL error (1205: Lock wait timeout exceeded). Has anyone else run into this problem? Seems like a bug in the core to me. We have not made any modifications associated with search. Running a re-index when using MySQL Fulltext for search works fine.