Mikhail Efremov created IGNITE-26684:
----------------------------------------
Summary: Improve configuration update fail message
Key: IGNITE-26684
URL: https://issues.apache.org/jira/browse/IGNITE-26684
Project: Ignite
Issue Type: Improvement
Reporter: Mikhail Efremov
*Description*
If any exception during configuration update emerges e.g. with CLI command
{{node config update ...}} then we will see a response like this:
{code:java}
[defaultNode]> node config update "ignite.compute.threadPoolSize=10"
Trace ID: 1d2c7418-a1a6-4d5a-b865-0e32854a2a0d
Failed to apply configuration
{code}
This message doesn't tell anything about what did happen and what should be
fixed from a user side. In this particular case the root reason was
{{NullPointerException}} because for a reason during configuration HOCON file
parsing a tree node wasn't found. This cause is passed during tree visiting in
{{HoconPresentation.java:93}} ({{throw new ConfigurationApplyException("Failed
to apply configuration.", e);}} line). So, initially the cause was passed
through the exception object, but was missed as CLI response and isn't handled
with any suggestion nor help nor advise for a user.
*Motivation*
We should improve UX with reasoning (what was wrong, what place goes wrong with
user's thesaurus) and advising (how to fix, in what place).
*Definition of done*
The message is improved as described.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
