[SOLR-12464] reduce Overseer.close() logging (for non-Overseer leaders)

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 7.5, 8.0
• Component/s: logging
• Assignee: Christine Poerschke
• Reporter: Christine Poerschke
• Created: 07/Jun/18 15:37
• Updated: 24/Sep/18 08:02
• Resolved: 30/Jul/18 17:40

Description

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.

Issue Links

• is related to: SOLR-12462 ObjectReleaseTracker silently 'releases' untracked objects
• relates to: SOLR-12454 tweak Overseer leadership transition related logging