You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2018/12/13 18:44:00 UTC

[jira] [Created] (SOLR-13072) Management of markers for nodeLost events is broken

Andrzej Bialecki  created SOLR-13072:
----------------------------------------

             Summary: Management of markers for nodeLost events is broken
                 Key: SOLR-13072
                 URL: https://issues.apache.org/jira/browse/SOLR-13072
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: AutoScaling
    Affects Versions: 7.5, 7.6, master (8.0)
            Reporter: Andrzej Bialecki 
            Assignee: Andrzej Bialecki 


In order to prevent {{nodeLost}} events from being lost when it's the Overseer leader that is the node that was lost a mechanism was added to record markers for these events by any other live node, in {{ZkController.registerLiveNodesListener()}}.

On Overseer leader restart if the autoscaling configuration didn't contain any triggers that consume {{nodeLost}} events then these markers are removed. If there are 1 or more trigger configs that consume {{nodeLost}} events then these triggers would read the markers, remove them and generate appropriate events.

However, as the {{NodeMarkersRegistrationTest}} shows this mechanism is broken and susceptible to race conditions.

It's not unusual to have more than 1 {{nodeLost}} trigger because in addition to any user-defined triggers there's always one that is automatically defined if missing: {{.auto_add_replicas}}. However, if there's more than 1 {{nodeLost}} trigger then the process of consuming and removing the markers becomes non-deterministic - each trigger may pick up (and delete) all, none, or some of the markers.

So as it is now this mechanism is broken if more than 1 {{nodeLost}} trigger is defined.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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