Doug, et. al., At 2:48 PM -0800 1/31/06, Chris Schneider wrote: >Is there a work-around? Based on some other postings, I've increased >ipc.client.timeout to 300000 (5 minutes). Does this property also control the >timeout for the RPC call you describe above? If so, should I increase this >timeout further? Is there a better way for us to avoid getting caught by the >RPC timeout you describe? This crawl was only a medium-sized test. We hope to >execute a much larger crawl over the next few days.
I was unable to even get the indexing phase started; I would get a timeout right at the beginning. I tried increasing the ipc.client.timeout from 5 minutes to 10 minutes, but that didn't help. In desperation, I increased it to 30 minutes and went to walk the dogs. As it turned out, it apparently took 14 minutes for it to "compute the splits". The job is still running (34% complete). Thus, it does seem like Doug was right about this being the problem. This is actually the third time we've increased ipc.client.timeout to solve crawl problems. I wonder whether we should just set it to an hour or two until the problem in the code is fixed. I guess I could also look into fixing the problem myself :) Thanks for the help, Doug! - Chris -- ------------------------ Chris Schneider TransPac Software, Inc. [EMAIL PROTECTED] ------------------------
