[
https://issues.apache.org/jira/browse/IGNITE-26239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Mukhopadhyay resolved IGNITE-26239.
------------------------------------------
Resolution: Duplicate
> Improve validation error handling on cluster init
> -------------------------------------------------
>
> Key: IGNITE-26239
> URL: https://issues.apache.org/jira/browse/IGNITE-26239
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Assignee: Aditya Mukhopadhyay
> Priority: Major
> Labels: ignite-3
>
> When a validation error happens during cluster initialization, it is
> displayed as following:
> {noformat}
> [defaultNode]> cluster init --name=a
> IGN-CMN-65535 Trace ID: c2f5b2a7-302e-4bc4-8417-0e57a8e3843c
> Got error response from node "defaultNode": Join request denied, reason:
> <ERROR MESSAGE>
> {noformat}
> A few potential improvements:
> # The CMN-65535 error should be avoided. This isn’t some unknown condition,
> this is absolutely normal scenario. This might not even be an “error” in
> terms of the user scenario - not sure if this warrants an error code, etc.
> # The error message is full of useless and misleading info.
> ## “Got error response” exposes the CLI/REST inner workings and protocol.
> ## “Join request denied” - whose join, where?
> The error message format must be updated to clearly state the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
