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

Sami Siren edited comment on SOLR-3219 at 4/17/12 12:40 PM:
------------------------------------------------------------

bq. Can you tell me how to turn off SUSS logging?

Questions are best asked in the mailing lists. When using the JUL binding one 
can configure the required level for messages for a class like this:

<classname>.level=<LEVEL>

so for example:

org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer.level=SEVERE

                
      was (Author: siren):
    bq. Can you tell me how to turn off SUSS logging?

Questions are best asked in the mailing lists. When using the JUL binding one 
can configure the required level for messages for a class like this:

<classname>=<LEVEL>

so for example:

org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer$Runner=SEVERE

                  
> StreamingUpdateSolrServer is not quiet at INFO, but CommonsHttpSolrServer is
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-3219
>                 URL: https://issues.apache.org/jira/browse/SOLR-3219
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 3.5, 4.0
>            Reporter: Shawn Heisey
>            Priority: Minor
>
> When using CommonsHttpSolrServer, nothing gets logged by SolrJ at the INFO 
> level.  When using StreamingUpdateSolrServer, I have seen two messages logged 
> each time it is used:
> Mar 08, 2012 4:41:01 PM 
> org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer$Runner run
> INFO: starting runner: 
> org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer$Runner@6bf28508
> Mar 08, 2012 4:41:01 PM 
> org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer$Runner run
> INFO: finished: 
> org.apache.solr.client.solrj.impl.StreamingUpdateSolrServer$Runner@6bf28508
> I think one of these behaviors should be considered a bug.  My preference is 
> to move the logging in SUSS out of INFO so it is silent like CHSS.  If the 
> decision is to leave it at INFO, I'll just live with it.  A knob to make it 
> configurable would be cool, but that's probably a fair amount of work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]

Reply via email to