Re: Using Apache Ignite with Zookeeper

[monal sinha]

Thanks, so I don't need to open any port on my ignite cluster node? My zk
cluster is running on separate node.

On Thu, Apr 5, 2018, 4:39 PM Roman Shtykh  wrote:

> You can specify the port your zk is running on as shown in [1], and it
> should be opened
>
>
> https://apacheignite.readme.io/docs/cluster-config#zookeeper-based-discovery
>
> Roman
>
>
> On Thursday, April 5, 2018, 4:48:05 p.m. GMT+9, monalsinha <
> monalsi...@gmail.com> wrote:
>
>
> I am using Apche Ignite with zookeeper based discovery using curator
> framework.
> Do I need to open any port on my ignite node like TCP based discovery, in
> order for this to work?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ignite visor command issue on K8s cluster

[vbm]

Hi,

I have deployed 4 pods (ignite server) on a  K8s cluster. I am using ignite
2.3 docker image.
I have followed the steps from the  link
  . 

Inside the container, I can see the ignite process running with the config
file:

root5412  0 11:20 ?00:00:34 /docker-java-home/bin/java
-Xms512m -Xmx1536m -XX:+AlwaysPreTouch -XX:+UseG1GC
-XX:+ScavengeBeforeFullGC -XX:+DisableExplicitGC -DIGNITE_QUIET=true
-DIGNITE_SUCCESS_FILE=/opt/ignite/apache-ignite-fabric-2.3.0-bin/work/ignite_success_22e88558-2de7-4b54-b0c4-e958859baa57
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=49112
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-DIGNITE_HOME=/opt/ignite/apache-ignite-fabric-2.3.0-bin
-DIGNITE_PROG_NAME=/opt/ignite/apache-ignite-fabric-2.3.0-bin/bin/ignite.sh
-cp
/opt/ignite/apache-ignite-fabric-2.3.0-bin/libs/*:/opt/ignite/apache-ignite-fabric-2.3.0-bin/libs/ignite-indexing/*:/opt/ignite/apache-ignite-fabric-2.3.0-bin/libs/ignite-spring/*:/opt/ignite/apache-ignite-fabric-2.3.0-bin/libs/licenses/*
org.apache.ignite.startup.cmdline.CommandLineStartup
*file:tmp/ignite/ignite-config.xml*
root   866   271  0 12:32 ?00:00:00 grep ignite


>From inside the container, when I try to connect using same config file in
the ignite visor console. 

Command to connect to the cluster:
visor> open -cpath=/tmp/ignite/ignite-config.xml

+--+
| Status   | Connected |
| Ignite instance name |  |
| Config path  | /tmp/ignite/ignite-config.xml |
| Uptime   | 00:00:00  |
+--+
visor>
*visor> node
(wrn) : Topology is empty.*

When I do a curl request using below command, I get the list of topology as
expected.
curl 'http://10.254.61.219:8080/ignite?cmd=top' | jq

I think it is not able to discover the other pods. How to use the ignite
visor script in a K8s environment ? 

Regards,
Vishwas



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unsubscribe Me

[shaun_m]

Please unsubscribe me from the distribution list.

Re: TcpDiscoverSpi error connection refused

[Amir Akhmedov]

Hi Denis,

I had a similar logs before and I can confirm I got them when enabled
"debug" level but the log level "severe" was really confusing.

On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov  wrote:

> Neeraj,
>
> You probably enabled debug logging on the following package:
> *org.apache.ignite.spi.discovery.tcp*
>
> There is nothing wrong in these exceptions actually.
> The first connection refused exception happens because there are two hosts
> in the IP finder configuration, but when you start the first node, nobody
> is bound to the discovery port on the second host. So, you get *"Connection
> refused" *exception, when discovery SPI is trying to connect to the
> second host.
>
> If you see a message like this, then it means, that discovery finished its
> work successfully:
> *Topology snapshot [ver=1, servers=1, ...]*
>
> You can disable debug logging not to see these exceptions.
>
> The second exception is also doesn't mean anything bad.
> It only means, that some object was transferred to this node, and
> connection was suddenly closed.
>
> So, none of these exceptions mean anything bad.
>
> Denis
>
> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya :
>
>> Hi,
>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
>> stopped and disabled.
>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated
>> default-config.xml in both servers
>> My default-config.xml looks like below :
>> -default-config.xml
>> @ axlrate-node-1-
>> 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";>
>> 
>> > class="org.apache.ignite.configuration.IgniteConfiguration">
>> 
>> 
>> 
>>   
>> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>   
>> 
>>   
>>   axlrate-node-1
>>   axlrate-node-2
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>> 
>>
>> ---
>>
>> -default-config.xml
>> @ axlrate-node-2-
>> 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";>
>> 
>> > class="org.apache.ignite.configuration.IgniteConfiguration">
>> 
>> 
>> 
>>   
>> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>   
>> 
>>   
>>   axlrate-node-1
>>   axlrate-node-2
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>> 
>>
>> ---
>>
>>
>> When I try to start ignite on axlrate-node-1, I see the following error
>> at startup.
>>
>> ---log
>> on
>> axlrate-node-1---
>> [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send:
>> Connection refused (Connection refused)
>> java.net.ConnectException: Connection refused (Connection refused)
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net
>> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>> at java.net
>> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>> at java.net
>> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:589)
>> at
>> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1386)
>> at
>> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1349)
>> at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1169)
>> at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1016)
>> at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:860)
>> at
>> org.apache.

Re: Unsubscribe Me

[Steve Benedict]

Me as well.

On Sat, Apr 7, 2018 at 7:02 AM,  wrote:

> Please unsubscribe me from the distribution list.
>

RE: Unsubscribe Me

[Melnychenko Vladyslav]

Me too. All known links don't work.



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Steve Benedict 
Date: 4/7/18 20:29 (GMT+02:00)
To: user@ignite.apache.org
Subject: Re: Unsubscribe Me

Me as well.

On Sat, Apr 7, 2018 at 7:02 AM, 
mailto:shau...@verizon.net>> wrote:
Please unsubscribe me from the distribution list.

Re: Unsubscribe Me

[Simon Chapple]

Me too please, I can’t seem to find any workable unsubscribe link either.

> On 7 Apr 2018, at 18:42, Melnychenko Vladyslav  wrote:
> 
> Me too. All known links don't work.
> 
> 
> 
> Sent from my Samsung Galaxy smartphone.
> 
> 
>  Original message 
> From: Steve Benedict 
> Date: 4/7/18 20:29 (GMT+02:00)
> To: user@ignite.apache.org
> Subject: Re: Unsubscribe Me
> 
> Me as well. 
> 
> On Sat, Apr 7, 2018 at 7:02 AM,  > wrote:
> Please unsubscribe me from the distribution list.
> 

Re: Unsubscribe Me

[vkulichenko]

To unsubscribe from this list you should send an email to
user-unsubscr...@ignite.apache.org

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/