Hi, Do you have an idea where it could come from ?? the process seems to stay stuck ???
2009/02/12 16:35:01 started by root 2009/02/12 16:35:01 command: /data/solr/book/bin/commit 2009/02/12 16:35:02 ended (elapsed time: 1 sec) 2009/02/12 16:40:01 started by root 2009/02/12 16:40:01 command: /data/solr/book/bin/commit 2009/02/12 16:45:02 started by root 2009/02/12 16:45:02 command: /data/solr/book/bin/commit 2009/02/12 16:46:15 failed to connect to Solr server at http://books.com:8180/solr/book/update 2009/02/12 16:46:15 failed to connect to Solr server at http://books.com:8180/solr/book/update 2009/02/12 16:46:15 commit failed 2009/02/12 16:46:15 commit failed 2009/02/12 16:46:15 failed (elapsed time: 374 sec) 2009/02/12 16:46:15 failed (elapsed time: 73 sec) I've my configuration which are : <ramBufferSizeMB>32</ramBufferSizeMB> <maxMergeDocs>2147483647</maxMergeDocs> <maxFieldLength>10000</maxFieldLength> <writeLockTimeout>1000</writeLockTimeout> <commitLockTimeout>18500</commitLockTimeout> No autocommit I've a cron job on commit which start every five minutes. and without cache : <filterCache class="solr.FastLRUCache" size="0" initialSize="0" autowarmCount="0"/> <!-- queryResultCache caches results of searches - ordered lists of document ids (DocList) based on a query, a sort, and the range of documents requested. --> <queryResultCache class="solr.FastLRUCache" size="0" initialSize="0" autowarmCount="0"/> <!-- documentCache caches Lucene Document objects (the stored fields for each document). Since Lucene internal document ids are transient, this cache will not be autowarmed. --> <documentCache class="solr.FastLRUCache" size="0" initialSize="0" autowarmCount="0"/> Any idea would be excellent, thanks a lot, -- View this message in context: http://www.nabble.com/solr---failed-to-connect-to-Solr-server-at-tp21978941p21978941.html Sent from the Solr - User mailing list archive at Nabble.com.
