Re: Ignite servers are not connecting to the cluster

I have already tried to put ports as you mentioned to the configuration and also increase or decrease all timeouts add some other timeouts like networkTimeout, ackTimeut, connectionTimeout but no change in the behavior. Ports are exposed and they are reachable from all VM to any other VM. We build

HashMap warning when using PutAll()

We are using Ignite v2.8.0 and the C# client. Some of our operations use PutAll() to save a collection of items in a single operation. This operation is emitting the following warning into the log: 2020-06-10 15:04:14,199 [77] WRN [ImmutableClientServer] Unordered map java.util.HashMap is used

Re: Ignite servers are not connecting to the cluster

Hi, there are two things to check. First, add 47500 port number to all the addresses of your TcpDiscoveryVmIpFinder.addresses property. For instance, 10.0.2.4 needs to be changed to 10.0.2.4:47500. Second, double-check that every Docker VM exposes the following port numbers - 11211, 47100,

Re: Ignite concepts

Eugene, In such a case, I would go for the thin client for several reasons: - With the thick client (aka. standard client), you will come across several limitations if the servers are deployed on VMs, but the thick clients are running in a K8S environment. Those limitations are to be

Re: Non Distributed Join between tables

I am making a fair amount of assumptions: 1. aff_b means that table c has an affinity key that includes table b's id plus table c's id. Is that true? 2. I get that table c has a foreign key to table b. 3. You are doing puts to your caches, then use the sql query engine with

Re: Non Distributed Join between tables

Yes, table c is child of table b. But, It is redundant in my RDBMS, Would have other solution whitout changing my schema? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Non Distributed Join between tables

Is table c, a child of table b? You have: tbl_a tbl_b tbl_c --- - aff_a aff_b You want: tbl_a tbl_b tbl_c --- - aff_a aff_a You want a "cosmic parent" in this case it

Re: Non Distributed Join between tables

Sorry Ilya, in my first post had an error. My structure is the following: tbl_a tbl_b tbl_c --- - aff_a aff_b When I make: select * from tbl_a INNER JOIN tbl_b ON tbl_b.id = tbl_a.fk_id INNER JOIN tbl_c.fk_id = tbl_b.id -> Return

Ignite servers are not connecting to the cluster

Hello, We have 12 identical azure servers in one network, each 32cpu and 64G ram. Ignite is running as docker container (identical including config). 8 our servers are working fine. But 4 are working only sometimes - they cant join and even worse they are blocking also others. I have recreated

Re: ignite work dir

Hi Ilya, IGNITE_HOME is /opt/ignite and in ignite-log4j, the log file set to I don't have any issue on the server side. This is the exception I get on the client side: Caused by: class org.apache.ignite.IgniteCheckedException: Work directory does not exist and cannot be created: /ignite/work

Re: NPE during printing failure information

Hi, This looks like a communication problem. GridWorker [name=grid-nio-worker-tcp-comm-3 Make sure all nodes can see each other. Test it with a minimum number of nodes. If it still doesn't work then describe your test and send the full logs and Ignite condifg. Thanks, Alex --

Re: ignite work dir

Hello! I recommend setting the property workDirectory of IgniteConfiguration class to desired value. And leaving IGNITE_HOME and IGNITE_WORK_DIR not specified. This may still cause exception if your e.g. logging subsystem is configured to use /ignite/work. Need to see the exception. Regards, --

ignite work dir

Hi All, What's the best way to set ignite's work dir on the client side, considering that the client and server nodes run under different users. I am setting both IGNITE_HOME and IGNITE_WORK_DIR system variables (on client), but I am still getting the exception "/ignite/work" cannot be created.

Ignite persistence and activation

Hello. I am trying to implement ignite persistence but I stumbled upon the following problems/questions. It is required to activate the cluster, that much is clear but I have bootstrap code that is using technical caches that I do not want to persist and more problematic I need to use

Re: Need to sync two apache ignite cache DB using ip address

Hello! Yes, you should specify both local and remote addresses in discovery SPI section: https://apacheignite.readme.io/docs/tcpip-discovery#static-ip-finder Regards, -- Ilya Kasnacheev чт, 11 июн. 2020 г. в 15:07, rakshita04 : > So are you saying apache ignite automatically does that. > Do

Re: Need to sync two apache ignite cache DB using ip address

So are you saying apache ignite automatically does that. Do i need to configure the ip of the other node somewhere in xml file so that data keeps syncing? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Need to sync two apache ignite cache DB using ip address

Hello! There are ways to do that (affinity backup filter), but why would you want to? You are much better off relying on Ignite's data model when using Apache Ignite. Regards, -- Ilya Kasnacheev чт, 11 июн. 2020 г. в 15:02, rakshita04 : > Hi Ilya, > > I want one node to be master for all

Re: Need to sync two apache ignite cache DB using ip address

Hi Ilya, I want one node to be master for all entries. How can i achieve this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Need to sync two apache ignite cache DB using ip address

Hello! If you declare your caches as REPLICATED they will be kept in sync. One node will be master of half entries and the other will be master of the remaining half. Regards, -- Ilya Kasnacheev чт, 11 июн. 2020 г. в 14:36, rakshita04 : > Hi Team, > > We have 2 apache ignite DBs located at

Need to sync two apache ignite cache DB using ip address

Hi Team, We have 2 apache ignite DBs located at separate IPs and connected through TCP-ip connection. ne of this DB should work as master dB and on any change should sync to other apache ignite DB and update the entries accordingly. How can i achieve this ? what changes do i need to do in xml

Re: Check service location possible ?

Ah, of course, thanks. Den 2020-06-11 kl. 10:41, skrev Alex Plehanov: Hello, IgniteServices.service(String name) method return service instance if it's deployed locally or null. чт, 11 июн. 2020 г. в 11:16, Mikael >: Hi! Is there any good way to

Re: Check service location possible ?

Hello, IgniteServices.service(String name) method return service instance if it's deployed locally or null. чт, 11 июн. 2020 г. в 11:16, Mikael : > Hi! > > Is there any good way to detect if a service is running local or remote > ? I guess I could check the instance of the returned proxy and

NPE during printing failure information

Hello, We start test our system on Ignite 2.8.1 and got very strange log. As I understand, It was error in system (on 2.7.6 this test works without any problem, I will investigate it later) and it was NPE during handling of this error:  [01:08:11] Configured failure handler:

Check service location possible ?

Hi! Is there any good way to detect if a service is running local or remote ? I guess I could check the instance of the returned proxy and see if it is the implementation class or not, but it feels a bit ugly, is there some other nicer way to do this ?

RE: Re:RE: Gridgain8.7.14 in kubernetes problem

This is just a workaround. Delete your ignite cluster and all the related PV'sand later install with different service name Or you can also try to re-deploy with persistence off Regards, Ravi Saxena Stay home stay safe From: s [mailto:13581902...@163.com] Sent: Thursday, June 11, 2020 8:13

Re: Ignite concepts

Thanks for getting back to me on this Dennis, The company's Ignite Cluster is already up and running on VMs on our company network. The service my team is standing up will run in our Private cloud K8S environment. Regarding our usecase we will have say 2 or 3 caches, our service will be passed 3