<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Drupal Search Funkiness</title>
	<atom:link href="http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/</link>
	<description>ce n'est pas la connaissance.</description>
	<pubDate>Mon, 01 Dec 2008 21:27:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: BigEric</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-193022</link>
		<dc:creator>BigEric</dc:creator>
		<pubDate>Thu, 11 Sep 2008 22:06:46 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-193022</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Good work-around&#8230;I boosted it up a bit as I have 150k nodes so we&#8217;ll see if we get a time out <img src='http://www.darcynorman.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolando</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-183599</link>
		<dc:creator>Rolando</dc:creator>
		<pubDate>Wed, 18 Jun 2008 01:26:49 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-183599</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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&#8230;. so it was something like 34 items left, 17 items left, 8 items left, 4 items left, 2 items left, then 0 items left. </p>
<p>I consider this to be very odd and unintended behavior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rillaith</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-160910</link>
		<dc:creator>Rillaith</dc:creator>
		<pubDate>Thu, 03 Jan 2008 12:00:29 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-160910</guid>
		<description>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 &#38; 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.</description>
		<content:encoded><![CDATA[<p>Thanks so much for putting me on the right track for this. Your suggestion of reducing the index batch size worked - eventually - seems there&#8217;s also a delay while the cron_busy variable is true. Finally managed to get mine to restart reindexing - I&#8217;m now using cron to call the cron.php script every 2 minutes with a batch of 20! I can&#8217;t use a larger one as the max script execution time is specifically configured low on our server.</p>
<p>Just wanted to let you &amp; your readers know of another resolution for related issues - if you don&#8217;t have comments enabled, or a post ha no comments, a node won&#8217;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: <a href="http://drupal.org/node/139537" rel="nofollow">http://drupal.org/node/139537</a> - involves editing node.module to change c.last_comment_timestamp for COALESCE(c.last_comment_timestamp,0) in 4-5 separate GREATEST(&#8230;) statements. </p>
<p>Note that I&#8217;m on 4.7, but this was still an issue in 5 and patched/worked around for something relatively recent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-82268</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-82268</guid>
		<description>Thanks very much for this, I had the same problem and your fix worked for me too.
</description>
		<content:encoded><![CDATA[<p>Thanks very much for this, I had the same problem and your fix worked for me too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-82333</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-82333</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>hi, </p>
<p>when i open search module it show 39% is index and 459 items left for indexing so what should i do and how</p>
<p>and also its not showing Index site button, it just show </p>
<p>39% of the site has been indexed. There are 459 items left to index.</p>
<p>Items to index per cron run:</p>
<p>Minimum word length to index:</p>
<p>Minimum word length to search for :</p>
<p>so from where i should get reindex site button</p>
<p>with regard<br />
nilesh jain</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flanderz</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-83236</link>
		<dc:creator>Flanderz</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-83236</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Did you ever find out what was going on with this?  I&#8217;m experiencing similar problems.  I&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dnorman</title>
		<link>http://www.darcynorman.net/2006/06/07/drupal-search-funkiness/#comment-83238</link>
		<dc:creator>dnorman</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">1994888502#comment-83238</guid>
		<description>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...</description>
		<content:encoded><![CDATA[<p>I never found out the cause. Futzing with clicking &#8220;force re-index&#8221; and running cron.php seemed to make it go away, and it hasn&#8217;t come back since&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
