Re: 3rd Party Persistence and two phase commit

Hi Denis, Yes, I have already read the article you mentioned. But it shows an example where the primary data being changed is located on the same node, at least I understand it so. In my original understanding it was that each node creates its own connection to the 3rd database. But perhaps

Re: 3rd Party Persistence and two phase commit

Hi Denis, thanks for clarifying! Did I understand you correctly that in any cases all interactions with 3rd party database will occur only on the initial node and the sessionEnd method will be called only once on the initial node? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to identify if the data returned from cache is partial data due to multiple node failures in partitioned cache

Hi, We are using Ignite cache version 2.3 . We are using persistent cache in Partitioned Mode having 4 cluster node running. We have configured caches to have 1 backup. I understand that if there are more than one node failure at a time, then data present in the live cluster may not be

Re: 3rd Party Persistence and two phase commit

Covered here: http://gridgain.blogspot.com/2014/09/two-phase-commit-for-in-memory-caches.html — Denis > On Jan 10, 2018, at 8:27 AM, Denis Mekhanikov wrote: > > Hi Andrey! > > Actually,

Re: Migrating from Oracle to Apache Ignite.

The data will be distributed evenly among the node. You can read more on this here [1] or watch this video [2] [1] https://apacheignite.readme.io/v2.3/docs/data-grid [2] https://www.youtube.com/watch?v=G22L2KW9gEQ — Denis > On Jan 10,

Re: Migrating from Oracle to Apache Ignite.

Hi Andrew, Thanks for your reply. Hope the ticket will be on 2.4 Next question about replication. I have 3 node server with different machine/ip. How ignite replicate/distribution data between them? Whereas my application only access into one node. Please let me know if there something I

Re: Los Angeles Area Apache Ignite/Kubernetes Meetup

cross-posting to the user list > On Jan 10, 2018, at 3:17 PM, Dani Traphagen wrote: > > Hi everyone, > > > *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media > Services* on using Apache Ignite with Kubernetes! > > > You can read all the meetup

Los Angeles Area Apache Ignite/Kubernetes Meetup

Hi everyone, *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media Services* on using Apache Ignite with Kubernetes! You can read all the meetup details here along with the abstract description. Free

Re: String as value problem ?

Mikael, First of all, the trace should contain the cause with more details. What does it tell? If this doesn't help to figure our the reason of the failure, please show the cache configuration. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Force flush of IGFS to secondary file system in DUAL_ASYNC mode

Hi llya, Thanks a lot for the detailed answer. It's nice to know there is a clear path to achieve that flush. Greetings, Juan On Mon, Jan 8, 2018 at 4:33 AM, ilya.kasnacheev wrote: > Hello! > > After reviewing IGFS code, I think that you can do the following: > >

String as value problem ?

Hi! I must be doing something very wrong, I have a cache where I use a String as the value and Ignite go bonkers on me when it try to create the cache: SEVERE: Failed to initialize cache. Will try to rollback cache start routine. [cacheName=RTU_CFGS] class

Re: IgniteOutOfMemoryException when using putAll instead of put

Thanks for the quick response. I have observed similar behavior with 3rd party persistence read through IF I set indexed types for the cache. Test case - Load up the cache using put with 35,000 entries ( keys 1 -> 35,000). Read every key using Get(key) This is the use case that I want to use in

Re: 3rd Party Persistence and two phase commit

Hi Andrey! Actually, commit to the 3rd party database will be performed from the node, that initiated the transaction. So, there will be only one transaction on the backing database. Otherwise it is impossible to guarantee data consistency, as you noticed. Denis ср, 10 янв. 2018 г. в 18:58,

3rd Party Persistence and two phase commit

Hi all! We have a cache "Accounts". We use 3rd Party Persistence with Write-Through mode In the cache there are two accounts. Account width id = 1 is located on node A and account with id = 2 is located on node B. In a single transaction we want to transfer the amount of $100 from account 1 to

Re: Adding custom processor in Ignite Node

HI Thanks for your response. Actually I want to implement custom Thin Client Processor/Server which will process requests from multiple C++ thin Client which use TCP socket communication. The Client requests are to perform sql queries , cache gets and puts and Ignite Transaction operations. I

failed to find sql table for type:

Ignite.NET 2.3.0 I'm pulling data from another DB and loading into Ignite node started under .NET Core console app. After converting the datarows into binary objects and putting them into the cache, I both do a count as well as debug and see the objects in the cache with the correct data. I try

Re: Adding custom processor in Ignite Node

Hi, 1) Why do you want to implement your own processor? 2) Have you considered using Ignite's compute grid and other features instead? If yes, what problems do you anticipate? Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, cache.putAll() can't evict the entries from the batch it is working on, and you can get Ignite OOME. This is expected behavior because putAll get locks for all provided entry keys. That is critical: 1) for transactional caches and 2) any caches backed up by 3-rd party

Re: Apache Ignite best practice

Hello Sergey! You are using "NOT IN" in your query. This may cause performance drawback. Using JOIN TABLE() is recommended, as per https://apacheignite.readme.io/docs/sql-performance-and-debugging#section-sql-performance-and-usability-considerations Not sure about DELETE. I guess it might be OK

Re: Apache Ignite & unixODBC and truncating text

Ok, thank you very much for your time nad reply. So, if I understend corectly, this is bug of Apache Ignite. How much time will take to resolve and fix this problem? I will track progress :) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Index on a Long ?

Hi Michael, There is no need to create index on keys as ignite key-value storage already has naturally index for it underneath. It should be enough to register indexing types [1]. Would you please clarify the use case if there is any other questions? [1]

Re: Index on a Long ?

Hi Mikael, You can specify indexed types via CacheConfiguration#setIndexedTypes() method. For instance: CacheConfiguration ccfg = new CacheConfiguration<>(); ccfg.setIndexedTypes(Long.class, Person.class); Another possible way is DDL statement: // Create table based on PARTITIONED

Re: How possible we can get the reason why the ignite shut down itself?

hi All, Mistake, someone include the enterprise jar in class path by mistake, so auto shutdown, find from log eventually! Regards Aaron aa...@tophold.com From: aa...@tophold.com Date: 2018-01-10 12:21 To: user Subject: How possible we can get the reason why the ignite shut down itself? Hi

Re: ClassCastException using cache and continuous query

Hi Diego, It seems that your error is related to different class Loaders being used. I don't have an idea why this happens but please try to clean your "work" directory in Ignite home (IGNITE_HOME) after 1.8 -> 2.3 upgrade or set up a new IGNITE_HOME. Please share you node configs and

Adding custom processor in Ignite Node

Hi I would like a start a custom processor on Ignite Node. After exploring the source code, I have created a custom processor class that extends GridProcessorAdapter. I added the code to start custom processor just like other processors in IgniteKernal.java passing the GridKernalContextImpl ctx

Re: Migrating from Oracle to Apache Ignite.

Hi, 1. SQL will support transactions after next ticket will be resolved [1]. You can track it's state via "start watching this issue" link on issue page. 2. JDBC pooling, failover and load banacling is not supported for JDBC. More over JDBC connection is not thread safe. Feel free to create a

Re: How possible we can get the reason why the ignite shut down itself?

Hi Aaron! Does the whole node stop, or only a single cache? Make sure, that you don't call *Ignite.close()* or *IgniteCache.close()* anywhere or use it as a resource in a try-with-resources block. Logs may contain useful information about the node failure. Try analysing it or attach it to the

Re: Are services serialized ?

Hi Mikael! Services along with *ServiceConfiguration* are put into a replicated system cache, so they are serialized at the moment of deployment and sent to all nodes in the cluster. When service is deployed, it is deserialized. So, if you have a field, that stores a socket instance, it's better

Are services serialized ?

Hi! How are services started on a node ? say a node goes down so a service must be started on another node, will it send the serialized service object I used at deployment or will it create a new instance of it in the other node ? And are services serialized for some other reasons ? do I

Re: Connection problem between client and server

Hi Jeff. Looks like my letter wasn't noticed by the developer community. I sent a message to the dev list one more time: http://apache-ignite-developers.2346864.n4.nabble.com/Irrelevant-data-in-discovery-messages-td25927.html In the meanwhile make sure, that this is really the cause of the

Re: Creating multiple Ignite grids on same machine

Hi Raymond, In your case you should configure: 1. different TcpDiscoverySpi local ports 2. different ports for TcpDiscoveryVmIpFinder (Vm = Static for .NET). You should not use a default ipFinder. 3. different TcpCommunicationSpi local ports Please see sample Java xml-configs as a reference