GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/1179 IGNITE-1943 ignitevisorcmd: wrong behavior for "mclear" command
Functional tests execution result:
visor> node
Select node from:
=======================================================================================
Node ID8(@), IP Node Type Up Time CPUs CPU Load Free Heap
=======================================================================================
0 425097BD(@n0), 192.168.0.103 Server 00:00:34 4 0.50 % 92.00 %
1 27906F97(@n1), 192.168.0.103 Server 00:00:28 4 1.17 % 93.00 %
---------------------------------------------------------------------------------------
Choose node number ('c' to cancel) [0]: c
visor> mclear
visor> mlist
Memory is empty.
visor> node
Select node from:
=======================================================================================
Node ID8(@), IP Node Type Up Time CPUs CPU Load Free Heap
=======================================================================================
0 425097BD(@n0), 192.168.0.103 Server 00:00:46 4 0.50 % 92.00 %
1 27906F97(@n1), 192.168.0.103 Server 00:00:40 4 0.53 % 93.00 %
---------------------------------------------------------------------------------------
Choose node number ('c' to cancel) [0]: c
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/samaitra/ignite IGNITE-1943
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1179.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1179
----
commit 5a96e426148e997958bc4397cad9f06c594e5041
Author: samaitra <
[hidden email]>
Date: 2016-10-23T08:15:00Z
IGNITE-1943 ignitevisorcmd: wrong behavior for "mclear" command
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---