You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2015/06/01 18:14:17 UTC

[jira] [Commented] (SOLR-7615) Slow update requests not logged at WARN due to how LogUpdateProcessor's are created

    [ https://issues.apache.org/jira/browse/SOLR-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567502#comment-14567502 ] 

Mark Miller commented on SOLR-7615:
-----------------------------------

I ran into something like this before. I was tempted to fix it as a bug. Seems to me it should be created at INFO or lower as well.

It's just a bit trappy. Perhaps we should always be creating it.

> Slow update requests not logged at WARN due to how LogUpdateProcessor's are created
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-7615
>                 URL: https://issues.apache.org/jira/browse/SOLR-7615
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>            Priority: Minor
>
> In SOLR-6650, we introduced the ability to only have slow update and query requests get logged as warnings. However, when tracking down the cause of SOLR-7603, we discovered that the LogUpdateProcessor is only included in the chain if the log has INFO enabled, thus rendering the solution provided by SOLR-6650 useless for update requests (queries still work though).
> Thus, we need to fix how LogUpdateProcessor is created if the user has configured slowUpdateThresholdMillis > 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org