Concurrent filter applications

[mcraven]

I have noticed that since upgrading to version 10 I cannot get my test site to successfully re-index itself. The indexing starts then the whole machine seems to lock up. I am running under Windows 2003 Server R2. When I launch Process Explorer I see that there are 10 copies of the mindtouch.deki.filter.exe program running and 99% of the CPU time is being spent in the hardware interrupt handler. What is going on? How do I limit the number of concurrent filter applications that can run?

Regards,
Mark C.

[mcraven]

Just upgraded to 10.0.3a and still see the same issue. Indexing never completes and Process Explorer show over 90% of the CPU time is being spent in the hardware interrupt handler. What is going on? As it stand now I cannot update my online instance until this issue us resolved.

Also whenever I start Deki I get the following error:

-------------------- initializing
-------------------- initialized 17.7468705 secs
-------------------- ready 4.7818354 secs
2010-11-02 09:17:18,396 [DispatchThread #24] WARN  MindTouch.Deki.Data.Caching.C
achingDekiDataSessionFactory - Caching module is disabled because license lacks
capability

I know I am running a Core license but why does it have to display this warning message?

Regards,
Mark C.

[mcraven]

Updated to version 10.0.4 and am still seeing the same issue. Once the indexing starts I can no longer get the site to respond. Is anyone else seeing this issue under Windows? Until this issue is resolved version 10 is useless to me.

Regards,
Mark C.

[mcraven]

OK, I went into mindtouch.deki.startup.xml and set <indexer-parallelism> to 4 down from its default of 10 and now things seem to be working better. There still seems to be times when the system gets stuck for a while with the hardware interrupts pegged at over 90% but eventually it frees up. I have also noticed the <indexer-parallelism> does not seem to be an absolute number. At times I have noticed 5 or even 6 filter tasks running at once. I sure would like to know what the root problem is.

Regards,
Mark C.

[mcraven]

I am now trying 10.00.5 and the same issue persists. During re-indexing a filter application will enter a state where it causes the hardware interrupts to go to near 100%. The system will be virtually locked up until I either kill the process or it times out. As it stands this make Olympic virtually of no use to me. I cannot upgrade until this issue is resolved. Am I the only one seeing this issue under Windows? I have tried to enter it into the bug tracking system but my account has been downgraded to a view only account.

Some help on this issue would be greatly appreciated.

Regards,
Mark C.

[SteveB]

Updated the bug report. Make sure to install the latest PDF iFilter.

[mcraven]

OK. I updated my PDF iFilter and the CPU utilization no longer maxes out. But what does remain is sometimes a mindtouch.deki.filter.exe task will launch but is just stalls. Process Explorer show zero CPU utilization for the task and it just stays there until the timeout occurs. Any idea what is going on?

Regards,
Mark C.

[mcraven]

I have noticed another thing. When I re-index my system drive started filling up. I went to C:\WINDOWS\temp and there were thousands of temp file. Some of them 0 bytes in size; some were quit large and had recognizable extensions. During the re-indexing I can watch these files being created. My question is shouldn't the indexing process delete these temp files when it completes? Something definitely seems to have changed with indexing under version 10.

Regards,
Mark C.

[mcraven]

Installed version 10.1 and am still seeing the same problem. Am I the only one who is seeing this problem?

Regards,
Mark C.

[straderw]

Well your not the only one. I have been having Indexing and Search issues like crazy lately.

I am on a Linux Server running 10.0.8 now... whenever a rebuild of the index happens. the 2 CPU's go to 100% bringing the site to it's knees if it even responds. Also I am finding that some articles aren't even being indexed... or at least arn't showing up in search results. So... my hard drive is fine... but the CPU is killing me.