lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Collins (JIRA)" <>
Subject [jira] [Commented] (SOLR-5563) Tone down some SolrCloud logging
Date Fri, 20 Dec 2013 08:58:07 GMT


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 and
"A cluster state change" (from are really useful to us, without those
we would never have been able to debug our latest issue (which we should be logging later

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:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message