[
https://issues.apache.org/jira/browse/IGNITE-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820861#comment-16820861
]
Ignite TC Bot commented on IGNITE-11735:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3580025]]
* IgniteClientCacheStartFailoverTest.testClientStartCloseServersRestart (last
started)
{color:#d04437}Scala (Visor Console){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3579997]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3580076&buildTypeId=IgniteTests24Java8_RunAll]
> Safely handle new closures of IGNITE-11392 in mixed cluster environment
> -----------------------------------------------------------------------
>
> Key: IGNITE-11735
> URL: https://issues.apache.org/jira/browse/IGNITE-11735
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Rakov
> Assignee: Denis Chudov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Under IGNITE-11392 we have added two new closures
> (FetchActiveTxOwnerTraceClosure and TxOwnerDumpRequestAllowedSettingClosure).
> In case we'll assemble mixed cluster (some nodes contain the patch, some
> don't), we may bump into situation when closures are sent to node that
> doesn't contain corresponding classes in classpath. Normally, closures will
> be deployed to "old" node via peer-to-peer class deployment. However, p2p may
> be disabled in configuration, which will cause ClassNotFoundException on
> "old" node.
> We should register IGNITE-11392 in IgniteFeatures (recent example:
> IGNITE-11598) and filter out nodes that don't support new feature before
> sending compute.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
