[
https://issues.apache.org/jira/browse/SOLR-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853797#comment-13853797
]
Daniel Collins commented on SOLR-5563:
--------------------------------------
Just a note, we are still in the process of trying to debug some cloud-related
issues that we only see in production, and messages like the Watcher (from
ConnectionManager.java) and "A cluster state change" (from ZKStateReader.java)
are really useful to us, without those we would never have been able to debug
our latest issue (which we should be logging later today).
I know we could configure logging to enable some debug trace in specific
components, but we then need to go through all the components and work out
which ones we need to enable. but I would just urge some caution on this
before committing IMHO. SolrCloud issues are still being reported issues on the
list, so there still seem to be some issues related to the Overseer that
haven't been caught yet.
Just my tuppence worth :)
> Tone down some SolrCloud logging
> --------------------------------
>
> Key: SOLR-5563
> URL: https://issues.apache.org/jira/browse/SOLR-5563
> Project: Solr
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Minor
> Attachments: SOLR-5563.patch
>
>
> We output a *lot* of logging data from various bits of SolrCloud, a lot of
> which is basically implementation detail that isn't particularly helpful.
> Here's a patch to move a bunch of stuff to #debug level, rather than #info.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
