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

2018-07-17 Thread Christine Poerschke (JIRA) 


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

Christine Poerschke updated SOLR-12464:
---
Fix Version/s: 7.5
   master (8.0)

> 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

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

2018-06-07 Thread Christine Poerschke (JIRA) 


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

Christine Poerschke updated SOLR-12464:
---
Attachment: SOLR-12464.patch

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

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

2018-06-07 Thread Christine Poerschke (JIRA) 


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

Christine Poerschke updated SOLR-12464:
---
Attachment: SOLR-12464-ea.patch

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org