Alexey Platonov created IGNITE-9829:
---------------------------------------
Summary: Add validation error 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
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)
