[
https://issues.apache.org/jira/browse/IGNITE-12036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900036#comment-16900036
]
Ignite TC Bot commented on IGNITE-12036:
----------------------------------------
{panel:title=Branch: [pull/6743/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4454063&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> 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)
