You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vasilisa Sidorova (JIRA)" <ji...@apache.org> on 2016/05/17 16:59:13 UTC
[jira] [Created] (IGNITE-3155) visorcmd: "open -d" doesn't work
Vasilisa Sidorova created IGNITE-3155:
------------------------------------------
Summary: visorcmd: "open -d" doesn't work
Key: IGNITE-3155
URL: https://issues.apache.org/jira/browse/IGNITE-3155
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 1.6
Environment: Ubuntu 14.04, Apache Ignite 1.6.0
Reporter: Vasilisa Sidorova
---------------------------------------------
DESCRIPTION
---------------------------------------------
When user try to connect to the grid with default config by command "open -d" nothing happens
---------------------------------------------
STEPS FOR REPRODUCE
---------------------------------------------
# Run node from IGNITE_HOME with default config (./config/default-config.xml) by command "./bin/ignite.sh -v"
# Run ignitevisorcmd.sh
# Connect visor to the grid by the command "open -d"
# Type "node"
---------------------------------------------
ACTUAL RESULT
---------------------------------------------
# Topology is empty
---------------------------------------------
EXPECTED RESULT
---------------------------------------------
# Message "Detailed statistics (y/n) [n]:" is presented
---------------------------------------------
ADDITIONAL INFO
---------------------------------------------
# Reproducible if visorcmd is started before node
# If the next step for presented scenario will be run node by command
{noformat}
./bin/ignite.sh -v ./examples/config/example-ignite.xml
{noformat}
Then topology will not be empty yet. But if scenario is:
** run node by command "./bin/ignite.sh -v ./examples/config/example-ignite.xml"
** run ignitevisorcmd.sh
** connect to the grid by the command "open -d"
** type "node"
the result will be the same - topology is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)