ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vyacheslav Koptilin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-12036) Changing baseline via set command may cause NPEs if configured NodeFilter takes node attributes into account
Date Mon, 05 Aug 2019 12:52:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-12036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vyacheslav Koptilin updated IGNITE-12036:
-----------------------------------------
    Fix Version/s: 2.8

> 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
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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