[
https://issues.apache.org/jira/browse/SOLR-12454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503886#comment-16503886
]
Christine Poerschke commented on SOLR-12454:
--------------------------------------------
{quote}... If you can isolate the added logging to log events that will only
occur during transition ...
{quote}
Yes, that is the intention – the logging is intended to assist not hinder and
ideally to assist out-of-the-box when someone hits overseer issues for the
first time e.g. due to (external) zookeeper hiccups of some sort.
In lieu of integration or regression tests, I just attached the
{{overseer-scenario-run.sh}} script I wrote for my own use to more easily
explore the scenarios i.e. {{download and unpack zookeeper, start external
zookeeper, start solr cloud, trigger overseer transition, stop solr, stop
zookeeper}} – that kind of thing.
+My next intended step+ is to consider both the proposed {{info}} as well as
the existing {{info}} logging for {{Overseer.java}} e.g. the {{Overseer
(id=null) closing}} logging emitted at the _start_ of apparently _every_ solr
node seems confusing?
{quote}... don't want another of those log lines spamming the startup sequence
or popping up every second just to say "I'm alive". ...
{quote}
I agree. Spammy logging can hinder log interpretation and troubleshooting.
{quote}... Also see related SOLR-12456 which I just filed ...
{quote}
Good find, thanks!
> 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, overseer-scenario-run.sh
>
>
> Proposed patch to follow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
