[
https://issues.apache.org/jira/browse/SOLR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532642#comment-13532642
]
Shawn Heisey commented on SOLR-4191:
------------------------------------
A closer look at the log has ruled out the idea that it's caused by merges.
The first two events are at 18:17 and 18:20. An optimize would have happened
at 18:00 on the only shard that gets new documents. With my mergePolicy and
updates happening once a minute, no merge could have happened at 18:17, and
even if I'm wrong about that, one definitely didn't happen at 18:20.
{noformat}
<mergePolicy class="org.apache.lucene.index.TieredMergePolicy">
<int name="maxMergeAtOnce">35</int>
<int name="segmentsPerTier">35</int>
<int name="maxMergeAtOnceExplicit">105</int>
</mergePolicy>
{noformat}
Next guess: it's purely a matter of timing.
> 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]
