ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3005) visorcmd: we need to improve alert command
Date Tue, 09 Aug 2016 12:32:29 GMT

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

Pavel Tupitsyn updated IGNITE-3005:
-----------------------------------
    Fix Version/s:     (was: 1.7)
                   1.8

> visorcmd: we need to improve alert command
> ------------------------------------------
>
>                 Key: IGNITE-3005
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3005
>             Project: Ignite
>          Issue Type: Improvement
>          Components: visor
>    Affects Versions: 1.5.0.final
>            Reporter: Pavel Konstantinov
>            Priority: Trivial
>             Fix For: 1.8
>
>
> Presently per-node alert prints in log it's info without node ID and user cannot understand
on what node that alert was triggered.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), spec=-r -t=10 -hu=gt10, created on=04/14/16,
14:59:19]
> {code}
> So we need to print out node ID8 in alert info for per-node alerts.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), spec=-r -t=10 -hu=gt10(12345678), created
on=04/14/16, 14:59:19]
> {code}
> where '12345678' after the text '-hu=gt10' is node ID8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message