[jira] [Updated] (IGNITE-25606) Fix failed node start handling with proper user messages instead of exceptions stacktraces

2025-07-18 Thread Mikhail Efremov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-25606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Efremov updated IGNITE-25606:
-
Priority: Trivial  (was: Minor)

> Fix failed node start handling with proper user messages instead of 
> exceptions stacktraces
> --
>
> Key: IGNITE-25606
> URL: https://issues.apache.org/jira/browse/IGNITE-25606
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Efremov
>Priority: Trivial
>  Labels: ignite-3
>
> *Description*
> From a user perspective if any error on an ignite node starting happens, then 
> node's logs will contain a lot of error stacktraces that aren't really useful 
> for the user. A better way is to print only messages with error codes.
> *Motivation*
> The main reason is to make on node starting failures logs more user friendly.
> *Definition of done*
> # On node starting failure there are no error stacktraces.
> # On node starting failure there are error messages with error codes only.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-25606) Fix failed node start handling with proper user messages instead of exceptions stacktraces

2025-07-17 Thread Mikhail Efremov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-25606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Efremov updated IGNITE-25606:
-
Description: 
*Description*

>From a user perspective if any error on an ignite node starting happens, then 
>node's logs will contain a lot of error stacktraces that aren't really useful 
>for the user. A better way is to print only messages with error codes.

*Motivation*

The main reason is to make on node starting failures logs more user friendly.

*Definition of done*

# On node starting failure there are no error stacktraces.
# On node starting failure there are error messages with error codes only.

  was:
*Description*

*Motivation*

*Definition of done*


> Fix failed node start handling with proper user messages instead of 
> exceptions stacktraces
> --
>
> Key: IGNITE-25606
> URL: https://issues.apache.org/jira/browse/IGNITE-25606
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Efremov
>Priority: Minor
>  Labels: ignite-3
>
> *Description*
> From a user perspective if any error on an ignite node starting happens, then 
> node's logs will contain a lot of error stacktraces that aren't really useful 
> for the user. A better way is to print only messages with error codes.
> *Motivation*
> The main reason is to make on node starting failures logs more user friendly.
> *Definition of done*
> # On node starting failure there are no error stacktraces.
> # On node starting failure there are error messages with error codes only.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)