Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06C171902F for ; Fri, 1 Apr 2016 04:07:26 +0000 (UTC) Received: (qmail 36604 invoked by uid 500); 1 Apr 2016 04:07:25 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 36510 invoked by uid 500); 1 Apr 2016 04:07:25 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 36481 invoked by uid 99); 1 Apr 2016 04:07:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 04:07:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 720402C14F6 for ; Fri, 1 Apr 2016 04:07:25 +0000 (UTC) Date: Fri, 1 Apr 2016 04:07:25 +0000 (UTC) From: "Vasiliy Sisko (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-2930) Visor cmd: alert does not react on condition switch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Vasiliy Sisko created IGNITE-2930: ------------------------------------- Summary: 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: Vasiliy Sisko Fix For: 1.6 @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 | => 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. {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)