You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Konstantinov (JIRA)" <ji...@apache.org> on 2017/08/09 07:18:00 UTC
[jira] [Commented] (IGNITE-5987) visorcmd: add possibility do not
close visorcmd in batch mode
[ https://issues.apache.org/jira/browse/IGNITE-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119518#comment-16119518 ]
Pavel Konstantinov commented on IGNITE-5987:
--------------------------------------------
Successfully tested.
My test is:
run visorcmd as daemon to register alert and monitoring it
{code}
screen -dmS visorcmd-register-alert ./ignitevisorcmd.sh -nq -b=register-alert.batch
{code}
register-alert.batch is
{code}
open -cpath=config/my-config.xml
alert -r -n=ALERT_NODE_DOWN -t=60 -nc=lt2 -s=./alert-node-down.sh
{code}
> visorcmd: add possibility do not close visorcmd in batch mode
> -------------------------------------------------------------
>
> Key: IGNITE-5987
> URL: https://issues.apache.org/jira/browse/IGNITE-5987
> Project: Ignite
> Issue Type: Bug
> Components: wizards
> Reporter: Pavel Konstantinov
> Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> That possibility will be useful for alert command which works only while visorcmd is active
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)