[
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: [email protected]
For additional commands, e-mail: [email protected]
