Re: Execution of local SqlFieldsQuery on client node disallowed
The error message says you're attempting to run the query on a client node. If that's the case (if the service is deployed on the client node), then the local flag has no effect because client nodes don't keep your data locally but rather consume it from servers. - Denis On Thu, Oct 22, 2020 at 6:26 PM narges saleh wrote: > Hi All, > I am trying to execute a sql query via a JDBC connection on the service > node (the query is run via a service), but I am getting *Execution of > local SqlFieldsQuery on client node disallowed.* > *The JDBC connection has the option local=true as I want to run the query > on the data on the local node only.* > *Any idea why I am getting this error?* > > *thanks.* >
Execution of local SqlFieldsQuery on client node disallowed
Hi All, I am trying to execute a sql query via a JDBC connection on the service node (the query is run via a service), but I am getting *Execution of local SqlFieldsQuery on client node disallowed.* *The JDBC connection has the option local=true as I want to run the query on the data on the local node only.* *Any idea why I am getting this error?* *thanks.*
Re: Isolating server nodes to a fixed virtual IP or interface
Hi Gilles, Thanks for considering Ignite for your project! Let's help to get you to production avoiding bumpy roads ) Try to set the 'localAddress' parameter (and 'localPortRanges' if needed) for both the discovery and communication settings: - Discovery: https://ignite.apache.org/docs/latest/clustering/network-configuration#discovery - Communication: https://ignite.apache.org/docs/latest/clustering/network-configuration#communication - Denis On Thu, Oct 22, 2020 at 10:54 AM Gilles wrote: > Hello, > > I'm currently moving a project from development stage to production. The > aim is that my cluster server nodes are running on multiple virtual private > servers, inside a VPN (10.0.0.0/24). > > But how do I make sure that I lock any communication of a node to either a > specific network interface, or a static virtual IP (eg 10.0.0.3)? > > Some googling got me to this answer from old documentation. > > > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> > > > > > However the nodes are still accessible on their public IP addresses. So > the question is, what is the correct way to isolate them from the public? > > I will be using a software firewall on these servers too, but I like to > have the peace of mind from the extra layer of security. > > > Thanks in advance, > Gilles > > And to the creators, maintainers and contributors, thank you so much for > this great piece of software! Never had so much fun doing "cumbersome" > database work. > > > >
Isolating server nodes to a fixed virtual IP or interface
Hello, I'm currently moving a project from development stage to production. The aim is that my cluster server nodes are running on multiple virtual private servers, inside a VPN (10.0.0.0/24). But how do I make sure that I lock any communication of a node to either a specific network interface, or a static virtual IP (eg 10.0.0.3)? Some googling got me to this answer from old documentation. However the nodes are still accessible on their public IP addresses. So the question is, what is the correct way to isolate them from the public? I will be using a software firewall on these servers too, but I like to have the peace of mind from the extra layer of security. Thanks in advance, Gilles And to the creators, maintainers and contributors, thank you so much for this great piece of software! Never had so much fun doing "cumbersome" database work.
Re: Urgent - Using Paired Connections leading to Connection Refuse
Hello!
Even with unpaired connections you need communication ports available in
both directions, unless you enable communication via discovery feature.
Regards,
--
Ilya Kasnacheev
вт, 20 окт. 2020 г. в 21:31, zork :
> Hello,
>
> We are facing a critical issue with Ignite 2.8.
>
> We have two machines in same location running different ignite services.
> M1
> Ignite server (running on port 48500)
> Ignite client-1 (running on port 48100)
>
> M2
> Ignite client-2 (running on port 14050)
>
> Port opened between machines:
> M2 to M1 - 48500-48520, 48100-48200
> M1 to M2 - 14050
>
> Now, M2 is not able to connect to ignite cluster if I set
> usePairedConnections to true.
> If I have usePairedConnections to false in TCPCommunicationSPI then all
> works fine.
>
>
> Here is the related ignite config:
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> hkvaspsy-101:48500..48520
>
>
>
>
>
>
>
>class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
>
>
>
> Connection refused is noticed in the logs on ignite client-2.
>
> 15:04:06:443908|0327-01043:FFTracer_Ignite [class
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action
> {Failed
> to join to address [addr=DELVM-M1/10.101.131.171:48500, recon=false,
> errs=[java.net.ConnectException: Connection refused (Connection
> refused)]]}
> Thread {tcp-client-disco-msg-worker-#21%WebCluster%}
> 15:04:06:443975|0296-01043:FFTracer_Ignite [class
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action {Send
> join request [addr=DELVM-M1/10.101.131.171:48501, reconnect=false,
> locNodeId=de5d623c-2f6b-4c04-a589-e1812ed1e960]} Thread
> {tcp-client-disco-msg-worker-#21%WebCluster%}
> 15:04:06:444578|1556-01043:FFTracer_Ignite [class
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {ERROR} Action
> {Exception on joining: Connection refused (Connection refused)} Thread
> {tcp-client-disco-msg-worker-#21%WebCluster%}
> 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:607)
> at
>
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1545)
> at
>
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1507)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:708)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:603)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$1100(ClientImpl.java:141)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:2027)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1683)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$1.body(ClientImpl.java:302)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
>
> Could you please tell why it is failing in case usePairedConnection is set
> to true?
> Do we also need 48100-48200 ports opened from M1 to M2 as well?
>
> Thanks.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: [Meetup] Join Apache Ignite Virtual Q Session on October 20
Hi Igniters! Here's the video from our 1str Q session: https://youtu.be/EUKNYUUPTRw Many thanks to speakers, experts, and attendees. Please share, what do you think of the format? I hope, next time someone will make us a little presentation of their case :) Slides Communication via Discovery by Ivan - https://go.gridgain.com/rs/491-TWR-806/images/2020-10-08-Communication_via_Discovery.pdf What you can learn from your distributed data? by Ravil - https://go.gridgain.com/rs/491-TWR-806/images/2020-10-20-Distributed_ML.pdf Cheers, Kseniya пн, 19 окт. 2020 г. в 15:50, Kseniya Romanova : > Hi! Just a kind reminder: see you tomorrow! > > ср, 14 окт. 2020 г. в 13:00, Kseniya Romanova : > >> Hi, Igniters! >> >> The Q sessions after our tech talks were so inspiring that we’re >> focusing the next community gathering on answering your questions! On >> October 20, join a special community session and ask experts about Ignite >> features, configuration, and architecture. >> >> We will start with three 10-minute tech talks by Ignite developers. Then, >> you will have an hour to ask our pool of experts your Ignite questions. >> >> RVSP and check out the pool of experts (more are to come): >> https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/273921637/ >> >
