[
https://issues.apache.org/jira/browse/SOLR-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547000#comment-16547000
]
ASF subversion and git services commented on SOLR-12464:
--------------------------------------------------------
Commit f7aed2876076aa489bc227d6d8d2e8c6ac96d8a0 in lucene-solr's branch
refs/heads/master from [~cpoerschke]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f7aed28 ]
SOLR-12464: Reduce Overseer.close() logging (for non-Overseer leaders)
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
