You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Puchnin (JIRA)" <ji...@apache.org> on 2018/01/19 09:30:00 UTC
[jira] [Commented] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331989#comment-16331989 ]
Sergey Puchnin commented on IGNITE-3690:
----------------------------------------
As it was discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-not-friendly-for-Monitoring-tt20802.html#none)
let's split this activity into two steps and reserver next error ranges for the domains:
-- the phase 1
1. 10000-10499 UnExpected, UnKnown
2. 10500-12499 Cluster and Topology
10500-10599 Discovery
10600-10699 Segmentation
10700-10799 Node Startup
10800-10899 Communication
10900-10999 Queue
11000-11099 Activate, startup process
11100-11199 Base line topology
11200-11299 Marshaller
11300-11399 Metadata
11400-11499 Topology Validate
3. 12500-14199 Cache and Storage
12500-12599 Partition map exchange
12600-12699 Balancing
12700-12799 Long-running transactions
12800-12899 Checkpoint
12900-12999 Create cache
13000-13099 Destroy cache
13100-13199 Data loading & streaming
4. 14200-15699 SQL
14200-14299 Long-running queries
14300-14399 Parsing
14400-14499 Queries
14500-14599 Scan Queries
14600-14699 SqlLine
5. 15700-17099 Compute
15700-15799 Deployment
15800-15899 spi.checkpoint
15900-15999 spi.collision
11600-16099 Job Schedule
-- the phase 2
6. 17100-19199 Service
7. 19200-21199 Security
8. 21200-23199 ML
9. 23200-25199 Integrations
10. 25200-27199 WebConsole
11. 27200-29199 Vendor-Specific
27200-27299 GG
FYI: [~dmagda]
> Log Message Glossary
> --------------------
>
> Key: IGNITE-3690
> URL: https://issues.apache.org/jira/browse/IGNITE-3690
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.4
> Reporter: Denis Magda
> Assignee: Denis Magda
> Priority: Major
> Fix For: 2.5
>
>
> It's time for Ignite to create a page which lists ALL the log messages, their common causes and potential solutions.
> Probably it makes sense to assign an unique ID for the most well-know errors so that a user is able to look up an error in the glossary quicker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)