[
https://issues.apache.org/jira/browse/SOLR-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974514#comment-15974514
]
Shalin Shekhar Mangar commented on SOLR-10396:
----------------------------------------------
There's a comment in the NodeLostTriggerTest which says:
{quote}
// add a new node but remove it before the waitFor period expires
// and assert that the trigger doesn't fire at all
{quote}
I think that should be the other way round? i.e. we want to remove a node but
add it back before the waitFor expires.
Rest looks good to me. +1 to commit to autoscaling branch.
> Implement trigger support for nodeLost event type
> -------------------------------------------------
>
> Key: SOLR-10396
> URL: https://issues.apache.org/jira/browse/SOLR-10396
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Cao Manh Dat
> Labels: autoscaling
> Fix For: master (7.0)
>
> Attachments: SOLR-10396.patch
>
>
> Implement support for 'nodeLost' event type in triggers. This kind of trigger
> is fired when a node goes away (i.e. no longer live) and does not comes back
> within a configured amount of time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
