You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org> on 2012/03/09 01:37:58 UTC
[jira] [Commented] (SOLR-3219) StreamingUpdateSolrServer is not
quiet at INFO, but CommonsHttpSolrServer is
[ https://issues.apache.org/jira/browse/SOLR-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225720#comment-13225720 ]
Ryan McKinley commented on SOLR-3219:
-------------------------------------
bq. A knob to make it configurable would be cool, but that's probably a fair amount of work.
Any logging framework will let you decide if that component should show INFO or not.
I think the rationale behind showing it for SUSS is that it is starting up a pool of connections that are expected to run for a long while. But I don't really care if it stays or changes. 'Bug' seems extreme to me
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org