Re: visor keep trigger alert when condition no longer satisfied?

2016-04-13 Thread tracel
thanks Vasiliy!!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p4114.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: visor keep trigger alert when condition no longer satisfied?

2016-04-01 Thread Vasiliy Sisko
Problem reproduced. Created issue:
https://issues.apache.org/jira/browse/IGNITE-2930



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p3853.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: visor keep trigger alert when condition no longer satisfied?

2016-03-31 Thread Vasiliy Sisko
Hello @tracel

We are look into this issue.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p3838.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: visor keep trigger alert when condition no longer satisfied?

2016-03-30 Thread tracel
the alert was registered by "alert -r -t=15 -cc=gt2"



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p3773.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


visor keep trigger alert when condition no longer satisfied?

2016-03-30 Thread tracel
Hi forum,

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 |  => 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 |  => 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.

Is there something wrong with the alert setting? or it's simply a bug?

Thanks in advance!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.