ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11735) Safely handle new closures of IGNITE-11392 in mixed cluster environment
Date Thu, 18 Apr 2019 10:33:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820948#comment-16820948

Sergey Antonov commented on IGNITE-11735:

[~Denis Chudov] Changes looks good.

> 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: 0.5h
>  Remaining Estimate: 0h
> Under IGNITE-11392 we have added two new closures (FetchActiveTxOwnerTraceClosure and
> 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

View raw message