You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/31 19:38:00 UTC
[jira] [Commented] (IGNITE-8010) Validate marshaller mappings on
join
[ https://issues.apache.org/jira/browse/IGNITE-8010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670632#comment-16670632 ]
ASF GitHub Bot commented on IGNITE-8010:
----------------------------------------
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/5228
IGNITE-8010 Validate marshaller mappings on join.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8010
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5228.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5228
----
commit e2b42fdf308a13fa17b9e543261129666825d986
Author: Denis Mekhanikov <dm...@...>
Date: 2018-10-31T19:35:41Z
IGNITE-8010 Validate marshaller mappings on join.
----
> Validate marshaller mappings on join
> ------------------------------------
>
> Key: IGNITE-8010
> URL: https://issues.apache.org/jira/browse/IGNITE-8010
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Mekhanikov
> Assignee: Denis Mekhanikov
> Priority: Major
> Fix For: 2.8
>
>
> When a new node joins topology, it sends its marshaller mappings in a discovery join message.
> Additional validation should be implemented to make nodes with conflicting marshaller mappings be rejected from connecting to the cluster.
> Such procedure is already implemented for binary metadata. Marshaller mappings should be validated in a similar way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)