Comments on: Drupal Search Funkiness

By: Helio D.

Helio D. — Tue, 27 Oct 2009 10:49:13 +0000

Eric, if you can, I would be glad to see how your final select line stayed with your end clause. I am having trouble to properly implement your solution

By: Erich Luedtke

Erich Luedtke — Wed, 20 May 2009 20:53:53 +0000

I had this problem as well. Increasing the limit also solved the problem (temporarily). I had to find the root or the problem since the site was for CNN. Keep in mind this site is highly customized drupal environment via /sites/, but your problems may be caused from the same thing.

We are only indexing two types of nodes, ‘listings’ and ‘articles’. Everytime you create a listing or article in our system it creates multiple ‘pointer’ nodes which we are not indexing. It would index the first couple listing and articles fine but then stop and never move forward on each following cron. The limit was set to 500. What was happening is everytime it would find the ‘pointer’ nodes and try to index them, they wouldn’t be indexed. Then it would run again and select the same pointers. Only by increasing the limit to a size greater than the ‘pointer’ node count could it move forward. The problem is that the ‘pointer’ node count will forever be increasing, so upping the limit is not a good fix.

What we had to do: Move the /nodes/ module to /sites/ and add a type select ( AND (type = ‘article’ OR type = ‘listing’)) under the function, node_update_index(). Not elegant at all, but a must for our time constraints.

Good luck!

By: BigEric

BigEric — Thu, 11 Sep 2008 22:06:46 +0000

Good work-around…I boosted it up a bit as I have 150k nodes so we’ll see if we get a time out

Thank you

By: Rolando

Rolando — Wed, 18 Jun 2008 01:26:49 +0000

I had to manually run cron.php up to 7 different times to get it to 100% index all items. What I started to notice after the second time I manually ran cron.php and checked the Indexing status, the number of items remaining was always half of what it previously was…. so it was something like 34 items left, 17 items left, 8 items left, 4 items left, 2 items left, then 0 items left.

I consider this to be very odd and unintended behavior.

By: Rillaith

Rillaith — Thu, 03 Jan 2008 12:00:29 +0000

Thanks so much for putting me on the right track for this. Your suggestion of reducing the index batch size worked – eventually – seems there’s also a delay while the cron_busy variable is true. Finally managed to get mine to restart reindexing – I’m now using cron to call the cron.php script every 2 minutes with a batch of 20! I can’t use a larger one as the max script execution time is specifically configured low on our server.

Just wanted to let you & your readers know of another resolution for related issues – if you don’t have comments enabled, or a post ha no comments, a node won’t be indexed (even if the search status page shows 100%), due to a combination of a NULL from a JOIN, and 5.0.13 MySQL changing how GREATEST works when one of the values is NULL. The fix is buried here: http://drupal.org/node/139537 – involves editing node.module to change c.last_comment_timestamp for COALESCE(c.last_comment_timestamp,0) in 4-5 separate GREATEST(…) statements.

Note that I’m on 4.7, but this was still an issue in 5 and patched/worked around for something relatively recent.

By: david

david — Wed, 31 Dec 1969 17:00:00 +0000

Thanks very much for this, I had the same problem and your fix worked for me too.

By: Anonymous

Anonymous — Wed, 31 Dec 1969 17:00:00 +0000

hi,

when i open search module it show 39% is index and 459 items left for indexing so what should i do and how

and also its not showing Index site button, it just show

39% of the site has been indexed. There are 459 items left to index.

Items to index per cron run:

Minimum word length to index:

Minimum word length to search for :

so from where i should get reindex site button

with regard
nilesh jain

By: Flanderz

Flanderz — Wed, 31 Dec 1969 17:00:00 +0000

Did you ever find out what was going on with this? I’m experiencing similar problems. I’m curious to know if the site kept indexing after you fixed it with the initial large index per cron run setting. So far I can index 100% of the site with a setting of 500 since there are only 450 nodes.

By: dnorman

dnorman — Wed, 31 Dec 1969 17:00:00 +0000

I never found out the cause. Futzing with clicking “force re-index” and running cron.php seemed to make it go away, and it hasn’t come back since…