[
https://issues.apache.org/jira/browse/SOLR-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504833#comment-16504833
]
Christine Poerschke commented on SOLR-12464:
--------------------------------------------
The attached demo SOLR-12464-ea.patch in conjunction with the SOLR-12462.patch
shows the 'release of untracked object' behaviour when starting/stopping a
cloud (with external zookeeper, have not tried with embedded zookeeper).
SOLR-12464-ea.patch is _not_ intended to be committed.
> 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
>
>
> 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]
