[
https://issues.apache.org/jira/browse/SOLR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543119#comment-13543119
]
Shawn Heisey commented on SOLR-4191:
------------------------------------
I seem to be having much the same problem on my production Solr 3.5 servers.
http://pastie.org/private/o2ekh0drs4syqb6t8re4w
Some discussion on solr-user suggests that perhaps this exception happens when
the client closes the connection before the response is delivered. If that's
the case, I think that Solr should log an INFO message saying that's what
happened, and include the params of the request like it does when a request is
successful, so that the problem can be investigated.
As for why requests are taking long enough to encounter client disconnects, I
have theorized that it might be GC pauses. I'll have to turn on GC logging to
verify.
> Exceptions thrown when /admin/mbeans is accessed during update/commit
> ---------------------------------------------------------------------
>
> Key: SOLR-4191
> URL: https://issues.apache.org/jira/browse/SOLR-4191
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: solr-impl 4.1-SNAPSHOT 1421496 - ncindex - 2012-12-13
> 14:56:25
> Reporter: Shawn Heisey
> Fix For: 4.2, 5.0
>
> Attachments: solr-2012-12-14[1].log
>
>
> I am getting the following exceptions in quick succession in the solr log
> when /admin/mbeans is accessed at the moment that an update/commit is
> happening:
> ERROR - 2012-12-13 18:17:01.930; org.apache.solr.common.SolrException;
> null:org.eclipse.jetty.io.EofException
> ERROR - 2012-12-13 18:17:01.982; org.apache.solr.common.SolrException;
> null:org.eclipse.jetty.io.EofException
> WARN - 2012-12-13 18:17:01.984; org.eclipse.jetty.server.Response; Committed
> before 500 {msg=Broken pipe,trace=org.eclipse.jetty.io.EofException
> WARN - 2012-12-13 18:17:01.984; org.eclipse.jetty.servlet.ServletHandler;
> /solr/s0live/admin/mbeans
> java.lang.IllegalStateException: Committed
> I will attach the full solr log. Before SOLR-4135 was fixed, I got a *lot*
> of those exceptions, but these were far less common. Now these appear to be
> the only thing I am getting in my logs, which log4j is logging at WARN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
