Ignite 2.0 visor issue

[ignite_user2016 <ri...@gmail.com>]

Hello Igniters,

I downloaded Ignite 2.0 and run the client and server all works well however
when I try to get stats from visor, I cant get anything.

visor> top
Empty topology.

visor> cache -scan
(wrn) <visor>: No caches found.
(wrn) <visor>: Type 'help cache' to see how to use this command.

Not sure what has changed with visor, any help would be much appreciated
here.

My environment is JDK8, Windows 7 with Ignite 2.0

Thanks,
Rishi



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[Vasiliy Sisko <vs...@gridgain.com>]

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:
  <value>127.0.0.1:47500..47510</value>
That addresses should be available from system where visor cli is started.

Visor cli start internal node. So you should add address of visor cli into
discovery configuration:
  <value>IP Address 1</value>
  <value>IP Address 2</value>
  <value>IP Address 3</value>
  <value>IP Address 4</value>
  <value>Visor IP Address</value>



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p14038.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[Amit Pundir <am...@gmail.com>]

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 to run visor cli (from /opt/ignite directory) -
./bin/ignitevisorcmd.sh -cfg=config/default-config.xml


The contents of the config file (/opt/ignite/config/default-config.xml) - 

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans.xsd">
    
    <bean id="grid.cfg"
class="org.apache.ignite.configuration.IgniteConfiguration">

        <property name="discoverySpi">
                <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                        <property name="ipFinder">

<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                                        <property name="addresses">
                                                <list>                                                        
                                                        <value>IP Address
1</value>
                                                        <value>IP Address
2</value>
                                                        <value>IP Address
3</value>
                                                        <value>IP Address
4</value>
                                                </list>
                                        </property>
                                </bean>
                        </property>
                </bean>
        </property>
    </bean>
</beans>


/Please consider IP Address 1/2/3/4 as the correct IPs for my VMs./



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p13993.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[Alexey Kuznetsov <ak...@apache.org>]

Amit,

Could you provide config for node?

On Fri, Jun 16, 2017 at 4:18 PM, Amit Pundir <am...@gmail.com> wrote:

> Hi,
> I am also facing the same issue with visor on ignite 2.0.0.
> Could you please let me know what the resolution was at your end.
>
>
> Thanks
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p13869.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Alexey Kuznetsov

Re: Ignite 2.0 visor issue

[Amit Pundir <am...@gmail.com>]

Hi,
I am also facing the same issue with visor on ignite 2.0.0. 
Could you please let me know what the resolution was at your end.


Thanks



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p13869.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[ignite_user2016 <ri...@gmail.com>]

Found the issue dont worry about it..



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p12461.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.