You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (Created) (JIRA)" <ji...@apache.org> on 2012/03/09 01:13:56 UTC
[jira] [Created] (SOLR-3219) StreamingUpdateSolrServer is not quiet
at INFO, but CommonsHttpSolrServer is
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
[jira] [Issue Comment Edited] (SOLR-3219) StreamingUpdateSolrServer
is not quiet at INFO, but CommonsHttpSolrServer is
Posted by "Sami Siren (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3219) StreamingUpdateSolrServer is not
quiet at INFO, but CommonsHttpSolrServer is
Posted by "Sami Siren (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sami Siren resolved SOLR-3219.
------------------------------
Resolution: Won't Fix
> 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
[jira] [Commented] (SOLR-3219) StreamingUpdateSolrServer is not
quiet at INFO, but CommonsHttpSolrServer is
Posted by "Sami Siren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255509#comment-13255509 ]
Sami Siren commented on SOLR-3219:
----------------------------------
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3219) StreamingUpdateSolrServer is not
quiet at INFO, but CommonsHttpSolrServer is
Posted by "Shawn Heisey (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226584#comment-13226584 ]
Shawn Heisey commented on SOLR-3219:
------------------------------------
It's probably not a bug, then. A side question, if you happen to know... how can I get milliseconds in my timestamps?
Can you tell me how to turn off SUSS logging? I have a logging.properties file with the following in it:
# Logging level
.level=INFO
# Write to a file
handlers = java.util.logging.FileHandler
# Write log messages in human readable format:
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.ConsoleHander.formatter = java.util.logging.SimpleFormatter
# Log to the log subdirectory, with log files named idxbuild_log-n.log
java.util.logging.FileHandler.pattern = ./log/idxbuild_log-%g.log
java.util.logging.FileHandler.append = true
java.util.logging.FileHandler.count = 10
java.util.logging.FileHandler.limit = 4194304
> 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
[jira] [Commented] (SOLR-3219) StreamingUpdateSolrServer is not
quiet at INFO, but CommonsHttpSolrServer is
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ 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