Thanks for reply Shawn.

Below is snippet of jetty.xml and jetty-https.xml

jetty.xml:38:    <Set name="idleTimeout" type="int"><Property
name="solr.jetty.threads.idle.timeout" default="5000"/></Set>
/// I presume this one I should increase, But I believe 5 second is enough
time for 250 docs to add to solr.

jetty.xml:39:    <Set name="stopTimeout" type="int"><Property
name="solr.jetty.threads.stop.timeout" default="60000"/></Set>

jetty-https.xml:45:        <Set name="idleTimeout"><Property
name="solr.jetty.https.timeout" default="50000"/></Set>

I'm also seeing "DirectUpdateHandler2 Starting optimize... Reading and
rewriting the entire index! Use with care". Would this be causing delay
response from solr?

Thanks in advance,
Novin


On 14 April 2016 at 14:05, Shawn Heisey <apa...@elyograg.org> wrote:

> On 4/14/2016 4:40 AM, Novin Novin wrote:
> > I'm having error
> >
> >  when sending solr doc
> > mid15955728
> > org.apache.solr.client.solrj.SolrServerException: Timeout occured
> > while waiting response from server at:
> > http://localhost.com:8983/solr/analysis
>
> <snip>
>
> > Caused by: java.net.SocketTimeoutException: Read timed out
>
> You encountered a socket timeout.  This is a low-level TCP timeout.
> It's effectively an idle timeout -- no activity for X seconds and the
> TCP connection is severed.
>
> I believe the Jetty included with Solr has a socket timeout of 50
> seconds configured.  You can also configure a socket timeout on the
> HttpClient used by various SolrClient implementations.
>
> The operating system (on either end of the connection) may also have a
> default socket timeout configured, but I believe that these defaults are
> normally measured in hours, not seconds.
>
> Thanks,
> Shawn
>
>

Reply via email to