[
https://issues.apache.org/jira/browse/SOLR-12454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502988#comment-16502988
]
Daniel Collins commented on SOLR-12454:
---------------------------------------
The nature of Overseer problems we have seen, is that by the time we realize we
have lost the overseer, there is nothing more to do other than bounce to regain
a new one. What we need is logging before/during the loss of overseer.
[~janhoy], by on demand, did you mean dynamically after the fact, or just we
should have a custom logging configuration which would set those particular
debug statements to log permanently in our setup? The former wouldn't work
(see above), but I that latter might be something we could look at. I'm
curious how others deal with these kinds of issues, or do they fortunately not
have them :).
> 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
