Databases
StackOverflow2013
Postsdbo
POIntermittent connection timeouts to Solr server using SolrNet
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIntermittent connection timeouts to Solr server using SolrNet
    primarykey
    data
    text
    <p>I have a production webserver hosting a search, and another machine which hosts the Solr search server (on a subnet which is in the same room, so no network problems). All is fine >90% of the time, but I consistently get a small number of <code>The operation has timed out</code> errors.</p> <p>I've increased the timeout in the SolrNet init to <strong>30</strong> seconds (!)</p> <pre><code>SolrNet.Startup.Init&lt;SolrDataObject&gt;( new SolrNet.Impl.SolrConnection( System.Configuration.ConfigurationManager.AppSettings["URL"] ) {Timeout = 30000} ); </code></pre> <p>...but all that happened is I started getting this message instead of <code>Unable to connect to the remote server</code> which I was seeing before. It seems to have made no difference to the amount of timeout errors.</p> <p>I can see <em>nothing</em> in <em>any</em> log (believe me I've looked!) and clearly my configuration is correct because it works most of the time. Anyone any ideas how I can find more information on this problem?</p> <p><strong>EDIT:</strong></p> <p>I have now increased the number of HttpRequest connections from 2 to 'a large number' (I see up to 10 connections) - but this has had no discernible effect on this problem.</p> <p>The firewall is set to allow ANY connections between the two machines.</p> <p>We've also checked the hardware with our server host and there are no problems on the connections, according to them.</p> <p><strong>EDIT 2:</strong></p> <p>We're still seeing this issue.</p> <p>We're now logging the timeouts and they're mostly just over 30s - which is the SolrNet layer's timeout; some are 20s, though - which is the Tomcat default timeout period - which suggests it's something in the actual connection between the machines.</p> <p>Not sure where to go from here, though - they're on a VLAN and we're specifically using the VLAN address - response time from pings is ALWAYS &lt;1ms.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIan Grainger
    1. USIan Grainger
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIntermittent connection timeouts to Solr server using SolrNet
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwhat's you commit/optimize strategy?
      singulars
      1. POIntermittent connection timeouts to Solr server using SolrNet
      1. USMauricio Scheffer
    2. COHope this answers your question: We do a dataimporthandler delta once every 15 minutes; and a full import overnight. But I don't do any kind of optimization. I'm going to go and read up now... What would you suggest?
      singulars
      1. POIntermittent connection timeouts to Solr server using SolrNet
      1. USIan Grainger
    3. COHmm, had a read, and have just added a scheduled update?optimize=true every night after the full import... But TBH I don't believe that optimization's going to do much considering the timeout is over 30s and usually this returns in much less than a second.
      singulars
      1. POIntermittent connection timeouts to Solr server using SolrNet
      1. USIan Grainger
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload