[
https://issues.apache.org/jira/browse/SOLR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533097#comment-13533097
]
Shawn Heisey commented on SOLR-4191:
------------------------------------
I bumped logging to INFO and turned on infostream. That's been running
overnight, and not a single exception has been logged. I'm guessing that the
extra logging is throwing off the timing. I had thought it might make the
error MORE prevalent, but best guess is that now the updates take long enough
that the stats requests are all done before the critical code section. I'll
try changing the servlet javascript code to wait until a couple of seconds past
the minute, to try and make the collision more likely while logging is turned
up.
> 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.1, 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]
