[ 
https://issues.apache.org/jira/browse/SOLR-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christine Poerschke resolved SOLR-12464.
----------------------------------------
    Resolution: Fixed

> reduce Overseer.close() logging (for non-Overseer leaders)
> ----------------------------------------------------------
>
>                 Key: SOLR-12464
>                 URL: https://issues.apache.org/jira/browse/SOLR-12464
>             Project: Solr
>          Issue Type: Task
>          Components: logging
>            Reporter: Christine Poerschke
>            Assignee: Christine Poerschke
>            Priority: Minor
>             Fix For: master (8.0), 7.5
>
>         Attachments: SOLR-12464-ea.patch, SOLR-12464.patch
>
>
> ZkController.init creates an Overseer object:
> * If that object becomes overseer leader then its start method is called.
> * If the object does not become overseer leader then its close method is 
> called and that currently emits mildly confusing {{Overseer (id=null) 
> closing}} info logging -- confusing especially since this happens at node 
> startup.
> ZkController.init creates an Overseer object:
> * If that object becomes overseer leader then its start method is called and 
> (if assertions are enabled) ObjectReleaseTracker.track is called.
> * If the object does not become overseer leader then its close method is 
> called and (if assertions are enabled) ObjectReleaseTracker.release is called 
> despite ObjectReleaseTracker.track not having been called previously.



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

Reply via email to