[IGNITE-9829] Add validation errors distinction to TcpDiscoveryCheckFailedMessage

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0
• Component/s: messaging
• Labels: newbie
• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Alexey Platonov
• Created: 09/Oct/18 14:27
• Updated: 10/Feb/20 15:25

Description

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.

Issue Links

• is related to: IGNITE-9834 ClientImpl shouldn't fail JVM with 130 error code after node validation errors