Aditya Mukhopadhyay created IGNITE-26289:
--------------------------------------------
Summary: Reduce message verbosity and stacktrace printing for node
join issues
Key: IGNITE-26289
URL: https://issues.apache.org/jira/browse/IGNITE-26289
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 3.0.0-beta1
Reporter: Aditya Mukhopadhyay
Assignee: Aditya Mukhopadhyay
Fix For: 3.1
When a node fails to initialize , it prints a huge message and crashes.
{code:java}
IGN-CMN-65535 Trace ID: c2f5b2a7-302e-4bc4-8417-0e57a8e3843c
Got error response from node "defaultNode": Join request denied, reason: Join
request denied, because ...
^-- <error cause>{code}
A few potential improvements:
* 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?
** “reason: Join request denied” - repeated message
** No idea why a new line and “^--” are needed. Feels like it’s generally a
good practice to print single-line errors as much as possible.
* Would be better not to fail the nodes and probably not event print the stack
traces, although this is more minor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
