Re: general question

I've done it, but from time to time transaction doesn't roll back. Perhaps, its a known bug пт, 10 мар. 2017 г. в 9:31, Alexey Goncharuk : > Hi Aleksey, > > In order to ensure that a transaction is rolled back during a node failure, > you need to orchestrate messages

Re: general question

Hi Aleksey, In order to ensure that a transaction is rolled back during a node failure, you need to orchestrate messages in such a way that at least one participating node does not receive a prepare request. As an example, you can look at

Re: general question

DHT refers to server side cache. Near cache is a part of distributed cache, but not a part of DHT. -Val On Thu, Mar 9, 2017 at 3:39 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Probably, the reasoning for it is that near entries have distributed form, > i.e. they are kept in

Re: general question

it looks strange. Because, DHT = distributed чт, 9 мар. 2017 г. в 14:26, Alexander Fedotov : > I suppose, GridDistributedCacheEntry contains common logic for Near and DHT > entries, while > GridDhtCacheEntry is it's subclass and contains common logic for DHT >

Re: general question

I suppose, GridDistributedCacheEntry contains common logic for Near and DHT entries, while GridDhtCacheEntry is it's subclass and contains common logic for DHT entries. For more details check the class hierarchy. On Tue, Mar 7, 2017 at 3:07 PM, ALEKSEY KUZNETSOV wrote:

Re: general question

I've found GridDhtCacheEntry and GridDistributedCacheEntry, so they must have been of the same logic ? пт, 3 мар. 2017 г. в 15:03, Alexander Fedotov : > Yes, DHT stands for distributed hash table. > > On Fri, Mar 3, 2017 at 3:01 PM, ALEKSEY KUZNETSOV < >

Re: general question

Big thanx! пн, 6 мар. 2017 г. в 17:37, Andrey Gura : > You always can use opposite direct during finding solution: > > ignite.cluster().forDataNodes(C1.getName()).nodes().contains(N1) > > On Mon, Mar 6, 2017 at 5:01 PM, ALEKSEY KUZNETSOV > wrote: > >

Re: general question

You always can use opposite direct during finding solution: ignite.cluster().forDataNodes(C1.getName()).nodes().contains(N1) On Mon, Mar 6, 2017 at 5:01 PM, ALEKSEY KUZNETSOV wrote: > Again. My question was "How could we list all caches, residing on a > certain Ignite

Re: general question

Again. My question was "How could we list all caches, residing on a certain Ignite instance?". In other words, i want to make sure N1 doesn't contain C1 cache. Is there a function F() as following : F (N1) = null , F(N2) = C1. пн, 6 мар. 2017 г. в 16:54, Andrey Gura : >

Re: general question

Aleksey, node N1 must not contain C1 cache data (must not be affinity node for cache C1), but N1 node must to know about C1 cache (must jave C1 cache descriptor) in order to provide access to C1 cache from this node. On Mon, Mar 6, 2017 at 4:36 PM, ALEKSEY KUZNETSOV

Re: general question

Consider we've got N1 and N2 nodes.Configure cache context C1 with node filter, which filters out N1. Now, if you call cacheNames on either of ignite instances you get C1. But N1 node must not contain C1 cache. пн, 6 мар. 2017 г. в 16:32, Sergey Kozlov : > Hi Aleksey > > >

Re: general question

Yes, DHT stands for distributed hash table. On Fri, Mar 3, 2017 at 3:01 PM, ALEKSEY KUZNETSOV wrote: > Thank you so much! And the last one. I cannot find definition of DHT. Does > it stand for distributed ? In contrary to Local > > пт, 3 мар. 2017 г. в 13:51, Alexander

Re: general question

Thank you so much! And the last one. I cannot find definition of DHT. Does it stand for distributed ? In contrary to Local пт, 3 мар. 2017 г. в 13:51, Alexander Fedotov : > Probably, IgniteTxHandler#processDhtTxPrepareRequest is what you are > looking for. > Check

Re: general question

Probably, IgniteTxHandler#processDhtTxPrepareRequest is what you are looking for. Check the data flow from GridDhtTxPrepareRequest#nearWrites On Fri, Mar 3, 2017 at 1:19 PM, ALEKSEY KUZNETSOV wrote: > Ah, thanks! Which class is responsible for near cache

Re: general question

Ah, thanks! Which class is responsible for near cache synchronization ? пт, 3 мар. 2017 г. в 13:15, Alexander Fedotov : > Hi Aleksey, > > Local cache pertains only to the node where it's created and no data is > distributed to > or synchronized with other nodes,

Re: general question

Hi Aleksey, Local cache pertains only to the node where it's created and no data is distributed to or synchronized with other nodes, while near cache serves as a front end for a partitioned cache, storing recently requested data which is synchronized when it's changed on other nodes. On Fri,

Re: general question

Hi, What exactly do you observe and how do you configure it? As I understand the SPI should be called even if the peer-class-loading is disabled. I would suggest turning on logger’s debug mode for this implementation. — Denis > On Feb 20, 2017, at 7:48 AM, ALEKSEY KUZNETSOV

Re: general question

Hi Alexey, See how org.apache.ignite.internal.processors.cache.CacheEvictableEntryImpl.meta() is used by, e.g. org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy.touch() method that is calling when entry accessed. On Wed, Feb 15, 2017 at 6:10 PM, ALEKSEY KUZNETSOV

Re: general question

hmm, why and how EvictionManager tracks an entry ? вт, 14 февр. 2017 г. в 23:07, Andrey Mashenkov : > Hi Aleksey, > > EvictableEntry.meta is used by EvictionManager to track entry. > Actually it may contains Node of EvictionPolicy queue to manupulate queue > items in

Re: general question

Hi Aleksey, EvictableEntry.meta is used by EvictionManager to track entry. Actually it may contains Node of EvictionPolicy queue to manupulate queue items in more efficient way. On Tue, Feb 14, 2017 at 4:26 PM, ALEKSEY KUZNETSOV wrote: > need help. What is the use of

Re: general question

...and what is the use of inject ? пн, 13 Фев 2017 г., 17:28 Alexey Goncharuk : > Aleksei, > > This processor handles various @*Resource (@IgniteInstanceResource, > @CacheNameResource, ...) annotations for user-supplied objects, such as > tasks, jobs, entry

Re: general question

Aleksei, This processor handles various @*Resource (@IgniteInstanceResource, @CacheNameResource, ...) annotations for user-supplied objects, such as tasks, jobs, entry processors, etc. --AG 2017-02-13 12:42 GMT+03:00 voipp : > Hi, all ! What is the use of

Re: general question

Please have a look at BinarySchema and it's usages. Essentially this is a fingerprint of object fields in the order they were serialized, represented as [field name] -> [position] hash map. Consider and object with 3 fields - A, B, C. There could be 6 different schemas for it: [A, B, C], [A, C,

Re: general question

What is schema in your context? пн, 13 февр. 2017 г. в 10:50, Vladimir Ozerov : > Alex, > > FieldAccessor stores field positions for the given schema to allow for fast > field value lookup. > > On Fri, Feb 10, 2017 at 7:06 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com

Re: general question

Alex, FieldAccessor stores field positions for the given schema to allow for fast field value lookup. On Fri, Feb 10, 2017 at 7:06 PM, ALEKSEY KUZNETSOV wrote: > Guys, i have a question.Why do we store fields position information in > FieldAccessor before hashcode