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

Andrzej Bialecki  edited comment on SOLR-10515 at 5/24/17 3:01 PM:
-------------------------------------------------------------------

Patch for review:
* added ZK persistence of internal trigger state, to be able to re-generate 
events that were not yet fired (eg. due to {{waitFor}} limit).
* cleanup of TriggerEvent hierarchy and generics (basically, we don't need 
generics here).
* added unit tests for re-playing events from queue, and for re-creating events 
from restored internal state.

I left a lot of debug logging in this version, this will be cleaned up before 
merging.


was (Author: ab):
Patch for review:
* added ZK persistence of internal trigger state, to be able to re-generate 
events that were not yet fired (eg. due to {{waitFor}} limit).
* cleanup of TriggerEvent hierarchy and generics (basically, we don't need 
generics here).
* added unit tests for re-playing events from queue, and for re-creating events 
from restored internal state.

> Persist intermediate trigger state in ZK to continue tracking information 
> across overseer restarts
> --------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10515
>                 URL: https://issues.apache.org/jira/browse/SOLR-10515
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Andrzej Bialecki 
>              Labels: autoscaling
>             Fix For: master (7.0)
>
>
> The current trigger design is simplistic and keeps all the intermediate state 
> in memory. But this presents two problems when the overseer itself fails:
> # We lose tracking state such as which node was added before the overseer 
> restarted
> # A nodeLost trigger can never really fire for the overseer node itself
> So we need a way, preferably in the trigger API itself to save intermediate 
> state or checkpoints so that it can seamlessly continue on overseer restarts.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to