Re: Ingestion API socket timeout exception waiting for response code

2012-05-07 Thread Karl Wright
t was crawled >>>> (5) Crawl again >>>> >>>> Does the deletion happen OK? >>>> >>>> AFAIK, nothing has changed in the Solr connector that should affect >>>> the ability to delete. This test will confirm that it is still >>&

Re: Ingestion API socket timeout exception waiting for response code

2012-05-07 Thread Erlend Garåsen
930125433 connection 'Web crawler': Ingestion API socket timeout exception waiting for response code: Read timed out; ingestion will be retried again later If I take a further look in Simple History, it seems that this error is related to document deletion. I have tried to delete the d

Re: Ingestion API socket timeout exception waiting for response code

2012-04-27 Thread Erlend Garåsen
F cannot delete documents from Solr. A timeout occurs, and the job stops after a while. This is what I can see from the log: WARN 2012-04-20 18:24:30,373 (Worker thread '16') - Service interruption reported for job 1327930125433 connection 'Web crawler': Ingestion API socket tim

Re: Ingestion API socket timeout exception waiting for response code

2012-04-26 Thread Karl Wright
not delete documents from Solr. A timeout occurs, and >> the job stops after a while. >> >> This is what I can see from the log: >>  WARN 2012-04-20 18:24:30,373 (Worker thread '16') - Service interruption >> reported for job 1327930125433 connection 'Web

Re: Ingestion API socket timeout exception waiting for response code

2012-04-26 Thread Karl Wright
ete documents from Solr. A timeout occurs, and > the job stops after a while. > > This is what I can see from the log: >  WARN 2012-04-20 18:24:30,373 (Worker thread '16') - Service interruption > reported for job 1327930125433 connection 'Web crawler': Ingestion API

Ingestion API socket timeout exception waiting for response code

2012-04-26 Thread Erlend Garåsen
Ingestion API socket timeout exception waiting for response code: Read timed out; ingestion will be retried again later If I take a further look in Simple History, it seems that this error is related to document deletion. I have tried to delete the document manually by using curl from the