You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/05/29 09:19:00 UTC
[jira] [Commented] (IGNITE-13050) ClusterGroup that is recomputed
on topology change
[ https://issues.apache.org/jira/browse/IGNITE-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119430#comment-17119430 ]
Ignite TC Bot commented on IGNITE-13050:
----------------------------------------
{panel:title=Branch: [pull/7831/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=5327051&buildTypeId=IgniteTests24Java8_RunAll]
> ClusterGroup that is recomputed on topology change
> --------------------------------------------------
>
> Key: IGNITE-13050
> URL: https://issues.apache.org/jira/browse/IGNITE-13050
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, ClusterGroup comes in two favors:
> One is a static set of UUIDs which will not change, second is predicate that is recomputed over ALL nodes on EVERY operation. This has bitten our client because recomputing of ClusterGroup happens in tcp-communication thread clogging it and delaying every operation in cluster. This is a major problem.
> It would be nice if there was a ClusterGroup with predicate which would recompute once per topology affinity change. Bonus points if it precisely tracks current topology with zero delay or overrun.
> Would be nice to upgrade firstNode/lastNode predicates to that mechanism since now they are static - topology changes but firstNode/lastNode projections don't, they may point to absent node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)