[
https://issues.apache.org/jira/browse/SOLR-12454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503400#comment-16503400
]
Jan Høydahl commented on SOLR-12454:
------------------------------------
By dynamic I meant issuing the HTTP command in order to raise certain logging
to DEBUG level across the cluster. I'm not sure if overseer debugging is
something so common that we should bog down everyone with those low-level logs?
Anyone who had Overseer issues once or twice and want to catch the next one
could of course configure log4j2.xml if they don't want to run verbose ({{-v}})
for all of Solr.
That said, I have not analysed the proposed patch in detail. If you can isolate
the added logging to log events that will only occur during transition then it
may be ok. But I don't want another of those log lines spamming the startup
sequence or popping up every second just to say "I'm alive". Also see related
SOLR-12456 which I just filed to try to get rid of spammy DEBUG-level logging
from the overseer.
> tweak Overseer leadership transition related logging
> ----------------------------------------------------
>
> Key: SOLR-12454
> URL: https://issues.apache.org/jira/browse/SOLR-12454
> Project: Solr
> Issue Type: Task
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-12454.patch
>
>
> Proposed patch to follow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
