Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-9735 Umbrella JIRA for Auto Scaling and Cluster Management in SolrCloud
  3. SOLR-10602

Triggers should be able to restore state from old instances when taking over

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.1, 8.0
    • Component/s: SolrCloud
    • Labels:


      Currently if a user modifies a trigger then the old trigger is closed and unscheduled and replaced with a new trigger instance with updated properties. However, this loses the intermediate state that the trigger may have been tracking. For example, say there is a trigger for NodeAdded event with waitFor=5s and a new node is added to the cluster. While the trigger is waiting for 5s before firing, the user modifies the trigger to change the waitFor=2s. Doing this today will erase the state of the old trigger and the new trigger will never fire for the newly added node.

      We need to be able to restore state from old trigger instance before replacing it.


        1. SOLR-10602.patch
          14 kB
          Shalin Shekhar Mangar
        2. SOLR-10602.patch
          30 kB
          Shalin Shekhar Mangar



            • Assignee:
              shalin Shalin Shekhar Mangar
              shalin Shalin Shekhar Mangar


              • Created:

                Issue deployment