ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-5473) Create ignite troubleshooting logger
Date Tue, 13 Jun 2017 07:40:00 GMT
Alexey Goncharuk created IGNITE-5473:
----------------------------------------

             Summary: Create ignite troubleshooting logger
                 Key: IGNITE-5473
                 URL: https://issues.apache.org/jira/browse/IGNITE-5473
             Project: Ignite
          Issue Type: Improvement
          Components: general
    Affects Versions: 2.0
            Reporter: Alexey Goncharuk
            Priority: Critical
             Fix For: 2.2


Currently, we have two extremes of logging - either INFO wich logs almost nothing, or DEBUG,
which will pollute logs with too verbose messages.

We should create a 'troubleshooting' logger, which should be easily enabled (via a system
property, for example) and log all stability-critical node and cluster events:
 * Connection events (both communication and discovery), handshake status
 * ALL ignored messages and skipped actions (even those we assume are safe to ignore)
 * Partition exchange stages and timings
 * Verbose discovery state changes (this should make it easy to understand the reason for
'Node has not been connected to the topology')
 * Transaction failover stages and actions
 * All unlogged exceptions
(add more)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message