lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5823) Add utility function for internal code to know if it is currently the overseer
Date Thu, 06 Mar 2014 23:50:44 GMT

    [ https://issues.apache.org/jira/browse/SOLR-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923268#comment-13923268
] 

Hoss Man commented on SOLR-5823:
--------------------------------

SOLR-5795 is an example of why this is useful...

there will be a recurring scheduled task on every node, but when that scheduled task fires,
I want only the current overseer node to actually execute that task -- because the resulting
deleteByQuery will then be propogated to all the other nodes via the distributed update. 


If we just let the task run on ever node, or all the leader nodes, it will hammer the system
with redundent requests.  Alternately: if we just tried to coerce thedeletes to be non distibuted,
they wouldn't be consistent, and replicas could get out of sync.

> Add utility function for internal code to know if it is currently the overseer
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-5823
>                 URL: https://issues.apache.org/jira/browse/SOLR-5823
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>
> It would be useful if there was some Overseer equivalent to CloudDescriptor.isLeader()
that plugins running in solr could use to know "At this moment, am i the leader?" 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message