[jira] [Commented] (SOLR-10515) Persist intermediate trigger state in ZK to continue tracking information across overseer restarts

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-10515) Persist intermediate trigger state in ZK to continue tracking information across overseer restarts

Tim Allison (Jira)

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

Andrzej Bialecki  commented on SOLR-10515:
------------------------------------------

Keeping a map would require a deep clone to avoid in-place modifications, but I agree it would be less fragile. I'll look into it.

> 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)
>
>         Attachments: SOLR-10515.patch, SOLR-10515.patch
>
>
> 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: [hidden email]
For additional commands, e-mail: [hidden email]