ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2930) Visor cmd: alert does not react on condition switch
Date Fri, 06 May 2016 03:23:12 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273581#comment-15273581
] 

Pavel Konstantinov commented on IGNITE-2930:
--------------------------------------------

# Use branch 2930
# start ignite cluster with 2 nodes
# start visorcmd
# register alert: alert -r -t=5 -up=gt0
# start logging: log -l
# open work\visor\visor-log

observing:  three alerts, but should be only two
{code}
05/06/16, 10:17:21 | H/N/C|1   |2   |8   |^...................|
05/06/16, 10:17:25 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]
05/06/16, 10:17:25 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]
05/06/16, 10:17:25 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]
05/06/16, 10:17:31 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]
05/06/16, 10:17:31 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]
05/06/16, 10:17:31 | Alert [id=3e199a34(@a0), spec=-r -t=5 -ut=gt0, created on=05/06/16, 10:16:11]

{code}

> Visor cmd: alert does not react on condition switch
> ---------------------------------------------------
>
>                 Key: IGNITE-2930
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2930
>             Project: Ignite
>          Issue Type: Bug
>          Components: wizards
>    Affects Versions: 1.6
>            Reporter: Vasiliy Sisko
>            Assignee: Pavel Konstantinov
>
>  @tracel
> {code:xml}
> An alert register for "-cc=gt2", so that alert should be trigger when "cc" (total number
of available CPUs in the grid" is "gt" (greater than) 2.
> However, I found alert keep trigger when "cc" become 1, here's the log showing a cluster
of 3 nodes/CPUs, alert still triggerd after removing 2 nodes.
>     03/30/16, 18:02:42 | Log started.
>     03/30/16, 18:03:02 | H/N/C|3   |3   |3   |^...................|
>     03/30/16, 18:03:11 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:03:22 | H/N/C|3   |3   |3   |^...................|
>     03/30/16, 18:03:27 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:03:33 | H/N/C|2   |2   |2   |^...................|
>     03/30/16, 18:03:32 | <visor> => NODE_LEFT: id8=ab8c9433, ip=0:0:0:0:0:0:0:1%lo
>     03/30/16, 18:03:42 | H/N/C|1   |1   |1   |^...................|
>     03/30/16, 18:03:43 | H/N/C|1   |1   |1   |^...................|
>     03/30/16, 18:03:35 | <visor> => NODE_LEFT: id8=4c98fc66, ip=0:0:0:0:0:0:0:1%lo
>     03/30/16, 18:03:43 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:03:59 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:04:02 | H/N/C|1   |1   |1   |^...................|
>     03/30/16, 18:04:15 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:04:23 | H/N/C|1   |1   |1   |^...................|
>     03/30/16, 18:04:32 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:04:43 | H/N/C|1   |1   |1   |^...................|
>     03/30/16, 18:04:48 | Alert [id=93d32fb5(@a1), spec=-r -t=15 -cc=gt2, created on=03/30/16,
18:03:10]
>     03/30/16, 18:04:50 | Log stopped.
> {code}



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

Mime
View raw message