How to query cross-node Cache data with JDBC correlation?

[hulitao198758]

Hello, ask, apache ignite using JDBC thin client connection, use the select
the from the cache. The table where the name in (select the name from
otherCache. Table) when the returned result is data of the current
connection node, other nodes can't return of data, how to solve this problem



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

如何用jdbc 关联查询跨节点Cache数据

[hulitao198758]

Hello, ask, apache ignite using JDBC thin client connection, use the select
the from the cache. The table where the name in (select the name from
otherCache. Table) when the returned result is data of the current
connection node, other nodes can't return of data, how to solve this problem



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

Re: TcpDiscoverSpi error connection refused

[Neeraj Vaidya]

Hi Denis,
But this issue does not occur on node2 even if it is started before node1. I 
feel even otherwise this message related to Discovery of level SEVERE is a bit 
misleading. Wouldn’t it be visible when log level is anything higher than DEBUG 
 as well ? I agree this is not a functional issue as it only occurs at startup 
when performing discovery and gets cleared when a peer is discovered.

Regards,
Neeraj

Sent from my iPhone

> On 8 Apr 2018, at 01:58, Amir Akhmedov  wrote:
> 
> 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 
>>> 

Re: Ignite visor command issue on K8s cluster

[David Harvey]

You have 4 nodes running, but are they part of a single cluster?   If you
look at the log file for one of the server nodes, has it connected to 4
servers or only one?

PS.  I've found this avoids the need to look up the URL "bin/ignitevisor.sh
-cfg=$CONFIG_URI".

On Sat, Apr 7, 2018 at 8:40 AM, vbm  wrote:

> 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/
>

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.