ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Lapin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-12036) Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account
Date Fri, 02 Aug 2019 08:58:00 GMT
Alexander Lapin created IGNITE-12036:
----------------------------------------

             Summary: Changing baseline via set command may cause NPEs if configured NodeFilter
takes node attributes into account
                 Key: IGNITE-12036
                 URL: https://issues.apache.org/jira/browse/IGNITE-12036
             Project: Ignite
          Issue Type: Bug
            Reporter: Alexander Lapin
            Assignee: Alexander Lapin


VisorBaselineTask doesn't allow to add() offline baseline node, but allows to set() collection
of nodes where at least one is offline and doesn’t belong to current BLT. 
We should prohibit passing offline nodes to setBaselineTopology(…) (in case they are not
part of current BLT): otherwise we won't be able to calculate affinity in case NodeFilter
is configured.

 
 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message