You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Platonov (JIRA)" <ji...@apache.org> on 2018/10/10 12:32:00 UTC

[jira] [Updated] (IGNITE-9829) Add validation errors distinction to TcpDiscoveryCheckFailedMessage

     [ https://issues.apache.org/jira/browse/IGNITE-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Platonov updated IGNITE-9829:
------------------------------------
    Summary: Add validation errors distinction to TcpDiscoveryCheckFailedMessage  (was: Add validation error distinction to TcpDiscoveryCheckFailedMessage)

> Add validation errors distinction to TcpDiscoveryCheckFailedMessage
> -------------------------------------------------------------------
>
>                 Key: IGNITE-9829
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9829
>             Project: Ignite
>          Issue Type: Improvement
>          Components: messaging
>            Reporter: Alexey Platonov
>            Priority: Major
>             Fix For: 3.0
>
>
> There is no way to define validation error type during joining on client side after node validation on server side. TcpDiscoveryCheckFailedMessage just aggregates error messages to one string. For example: if there was auth error while joining then client receive TcpDiscoveryCheckFailedMessage instead of TcpDiscoveryAuthFailedMessage. This is due to server validation protocol supports just IgniteNodeValidationResult as string-wrapper without additional information about types of validation errors. Set of enum values representing validation errors may be good solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)