Hello @Amit Pundir
Visor show “Empty topology” message for “top” command when it can not find
nodes. Please check your discovery configuration. It should contain valid IP
addresses and ports. F.e. address format:
127.0.0.1:47500..47510
That addresses should be available from system where visor c
I am running Ignite on Linux. There are 4 VMs where I have set up Ignite. All
the VMs have exact same configuration. The details for one of the VM
configuration is below -
Installation directory - /opt/ignite
Command used to run ignite (from /opt/ignite directory) - ./bin/ignite.sh
Command used
Amit,
Please attach full config.
On Sun, Jun 18, 2017 at 2:15 AM, Amit Pundir wrote:
> Hi Everyone,
> I am using Ignite 2.0.0 and trying to launch the visorcmd cli. It shows the
> 'Connected' message but always outputs 'No caches found' message. The
> aforementioned cache exists on the cluster
Hi Everyone,
I am using Ignite 2.0.0 and trying to launch the visorcmd cli. It shows the
'Connected' message but always outputs 'No caches found' message. The
aforementioned cache exists on the cluster though as I can query it through
a java client.
The commands I use to run Ignite cache and the v
