Yes, get a thread dump of the agents process. On Windows, this is CTRL-break in the process window, on linux kill -QUIT <pid>. You should be able to find out what everything is waiting on. If you can, send me the dump and I can interpret it for you.
Karl On Tue, Jul 5, 2011 at 2:26 PM, Farzad Valad <[email protected]> wrote: > So I'm crawling with the new code, and the crawl job seems to be frozen. > CPU usage is near 0 for the agent process, nothing abnormal in the logs, > and the status says running in the UI. My crawl set is 47,000 files, in the > UI Documents=12122, Active=7144, and Processed=4978. According to the last > log entry, it's been frozen over an hour now. The data resides on the local > system, so I'm not dependent on the network for anything. > > Any ideas? >
