Re:

ribute-1.CreateGitHubpull-request > > > > P.S. > You’re welcomed to send messages like this to the dev list directly. There > is a plenty of folks which can assist you earlier. > > — > Denis > > > On Jan 31, 2017, at 3:42 AM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.c

Re: IGNITE-3244

out.unsafeWriteByte(GridBinaryMarshaller.OBJ_ARR); > > and right below we store the actual type > > > > out.unsafeWriteInt(desc.typeId()) > > > > In my understanding, in the layout of binary data we have all the data > > needed to deserialize an array back pr

Re: IGNITE-3244

Moreover, in CacheObjectBinaryProcessorImpl#marshalToBinary() we explicitly marshal objects array into Object[] and then write it further. I wonder why we dont just marshal -> unmarshal it ? пн, 6 февр. 2017 г. в 15:58, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > type IDs correc

Re: IGNITE-3244

I have a solution on this task, this is pull request into my forked repository : https://github.com/voipp/ignite/pull/6 пн, 6 февр. 2017 г. в 16:03, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Moreover, in CacheObjectBinaryProcessorImpl#marshalToBinary() we > explicitly marshal o

Test failures

We have a lot of failed tests, which is frustrating. Some of them are flaky(floating status randomly goes from succesful to failed) which adds to frustration. Perhaps, we should fix all the tests in first place, and then continue doing tickets ? -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-1178

will take https://issues.apache.org/jira/browse/IGNITE-1178 if you don't mind -- *Best Regards,* *Kuznetsov Aleksey*

Re: IGNITE-3244

mmunity. You might get a valuable feedback before getting down to coding. > > — > Denis > > > On Feb 1, 2017, at 1:18 AM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > > > will take https://issues.apache.org/jira/browse/IGNITE-3244 > &

Re: Test failures

that annoys you most? > > — > Denis > > > On Feb 7, 2017, at 8:40 AM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > > > We have a lot of failed tests, which is frustrating. Some of them are > > flaky(floating status randomly goes from succesful

Hello

Hello. Im new to Ignite -- *С уважением,* *Кузнецов Алексей* ЗАО «Сбербанк-Технологии» Тел. 789-12-074

IGNITE-3385

If you dont mind, i will take IGNITE-3385 ticket -- *Best Regards,* *Kuznetsov Aleksey*

Re: IGNITE-3385

utility, but we decided to drop > it in favor of Web Console. > Web Console also can import schema import and it is already do it much > better that Schema import utility. > > So, my advice to take another issue to start from. > > Thanks! > > > On Fri, Jan 27, 2017 at 4

IGNITE-4492

will take IGNITE-4492 if you don't mind -- *Best Regards,* *Kuznetsov Aleksey*

Re: IGNITE-4492

I know! But i don't have sufficient privileges yet пт, 27 янв. 2017 г. в 14:41, Alexey Kuznetsov <akuznet...@apache.org>: > Aleksey, > > FYI: You should assign issue in JIRA to your self. (click "Assign to me" > link). > > On Fri, Jan 27, 2017 at 6:28 PM,

Re: IGNITE-4492

https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Alexey+Kuznetsov пт, 27 янв. 2017 г. в 16:48, Alexey Kuznetsov <akuznet...@apache.org>: > What is your JIRA ID? > I will add you to Apache Ignite contributors. > > On Fri, Jan 27, 2017 at 7:34 PM, ALEKSEY KUZNETS

Re: newbie ticket issue

ntribute < > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute> > > > > Project setup in Intellij IDEAL > > https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup < > https://cwiki.apache.org/confluence/display/IGNITE/Proj

Re: IGNITE-4492

thanx пт, 27 янв. 2017 г. в 17:15, Alexey Kuznetsov <akuznet...@apache.org>: > Added to contributors. > > On Fri, Jan 27, 2017 at 9:04 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > https://issues.apache.org/jira/secure/ViewProfile.jspa?

PR IGNITE-2845 Get operation might ignore entry update from EntryProcessor

PR redy, welcome to review : https://github.com/apache/ignite/pull/1557 https://issues.apache.org/jira/browse/IGNITE-2845 -- *Best Regards,* *Kuznetsov Aleksey*

PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Plz, review my PR : https://github.com/apache/ignite/pull/1517 https://issues.apache.org/jira/browse/IGNITE-1178 -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-2626 Binary marshaller: sort fields alphabetically

im going to take https://issues.apache.org/jira/browse/IGNITE-2626 -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-2845 Get operation might ignore entry update from EntryProcessor

; entry processor result, which is typically smaller than the value stored > >> in > >> a cache. > >> > >> Looks like this case is covered by the following ticket: > >> https://issues.apache.org/jira/browse/IGNITE-3471. Please cooperate > with > >> Alexan

general question

Hi! Why local deployment SPI is ignored, if peer class loading is disabled, and local deployment spi is enabled ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Hi! Review my PR again, plz - https://github.com/apache/ignite/pull/1517 пт, 17 февр. 2017 г. в 14:44, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > thanx! my next PR review will be in up source > > пт, 17 февр. 2017 г. в 13:05, Alexey Goncharuk <alexey.goncha...@gmail.co

PR IGNITE-2552 EvictionPolicies refactored, logic changed

Plz, review my PR : http://reviews.ignite.apache.org/ignite/review/IGNT-CR-98 or https://github.com/apache/ignite/pull/1545 -- *Best Regards,* *Kuznetsov Aleksey*

Will take IGNITE-1264 Resource SPI

will take https://issues.apache.org/jira/browse/IGNITE-1264 -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-2552

will take https://issues.apache.org/jira/browse/IGNITE-2552 if you dont mind -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-1178

Plz, review my PR : https://github.com/apache/ignite/pull/1517 https://issues.apache.org/jira/browse/IGNITE-1178 -- *Best Regards,* *Kuznetsov Aleksey*

Re: IGNITE-4492

asfgit <https://github.com/asfgit> has closed my PR for somehow вт, 14 февр. 2017 г. в 14:46, Semyon Boikov <sboi...@gridgain.com>: > Thanks Aleksey, I'll review it today. > > On Tue, Feb 14, 2017 at 2:30 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wro

general question

need help. What is the use of EvictableEntry.meta ? Why do we need to ship some meta to entry ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: binary output from cache

s is much faster than deserializing the whole object. > > --AG > > 2017-02-10 10:26 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > How could it give perfomance improvement ? > > > > чт, 9 февр. 2017 г. в 23:21, Valentin Kulichenko < > > va

general question

Guys, i have a question.Why do we store fields position information in FieldAccessor before hashcode evaluation? Test example is in : org.apache.ignite.internal.binary.BinaryFieldIdentityResolverSelfTest#testHashCode -- *Best Regards,* *Kuznetsov Aleksey*

Re: general question

What is schema in your context? пн, 13 февр. 2017 г. в 10:50, Vladimir Ozerov <voze...@gridgain.com>: > 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 <

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: binary output from cache

more > complicated use cases, like when values are read on servers side, or when > it gives performance improvement. > > -Val > > On Thu, Feb 9, 2017 at 10:36 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > Guys, i have a dumb question.

Re: IGNITE-3244

and then write it > > further. I > > >> wonder why we dont just marshal -> unmarshal it ? > > > > > > This kind of legacy code that was there for a while. I can’t recall the > > reason why we have it but I’m sure there is a sense for that. > > > &g

Re: Test failures

ng some of them making the product more > stable? Basically, this should help your the internals even more profoundly. > > — > Denis > > > On Feb 7, 2017, at 11:50 PM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > > > How could they co-exist ? When you d

binary output from cache

Guys, i have a dumb question. Why do we need to set withKeepBinary()? What i mean is why dont we just have it hardcoded ? -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect.

will take the ticket https://issues.apache.org/jira/browse/IGNITE-2779 -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

thankx чт, 16 февр. 2017 г. в 11:29, Alexey Kuznetsov <akuznet...@apache.org>: > Hi! > > I did minor code-style review directly on GitHub. Please fix. > > But some one who knows GridCacheProcessor.java should do one more review. > > On Thu, Feb 16, 2017 at

IGNITE-2626 is cloned?

Hi! about https://issues.apache.org/jira/browse/IGNITE-2626. Im sure this ticket is cloned from https://issues.apache.org/jira/browse/IGNITE-3191, because it was implemented there. And im confused with code status : fields order is somehow deprecated. This ticket -

Re: IGNITE-2626 Binary marshaller: sort fields alphabetically

yeap чт, 16 февр. 2017 г. в 11:26, Vyacheslav Daradur <daradu...@gmail.com>: > Hello. > > Look at the ticket: https://issues.apache.org/jira/browse/IGNITE-4695 > - Write primitive fields before during binary object marshalling > > Maybe it relates. > > 2017

Re: general question

late queue > items in more efficient way. > > On Tue, Feb 14, 2017 at 4:26 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > need help. What is the use of EvictableEntry.meta ? Why do we need to > ship > > some meta to entry ?

PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Again, plz, review my PR : https://github.com/apache/ignite/pull/1517 https://issues.apache.org/jira/browse/IGNITE-1178 -- *Best Regards,* *Kuznetsov Aleksey*

Took IGNITE-2845 Get operation might ignore entry update from EntryProcessor.

https://issues.apache.org/jira/browse/IGNITE-2845 -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

e UpSource: > http://reviews.ignite.apache.org/ignite/ > > After you've registered, you should be able to open a review. > > --AG > > 2017-02-17 11:13 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > Again, plz, review my PR : https://github.com/apa

REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Plz, review my PR : http://reviews.ignite.apache.org/ignite/review/IGNT-CR-98 or https://github.com/apache/ignite/pull/1545 -- *Best Regards,* *Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

plz review ticket again пн, 20 февр. 2017 г. в 11:14, Alexey Goncharuk <alexey.goncha...@gmail.com>: > Thanks, Aleksey, > > I will take a look this week. > > --AG > > 2017-02-20 10:25 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > Hi! Re

PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Plz, review my changes https://issues.apache.org/jira/browse/IGNITE-1094 https://github.com/apache/ignite/pull/1581 -- *Best Regards,* *Kuznetsov Aleksey*

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

changes and have some comments (mostly cosmetic). > Could you please fix this comment? See review in Upsource for details. > > On Tue, Feb 28, 2017 at 2:17 PM, ALEKSEY KUZNETSOV > <alkuznetsov...@gmail.com> wrote: > > Plz, review my PR : > > http://reviews.ignite.apache.org

code refactoring suggestion

Hi all ! During pessimistic transaction we execute prepare phase at org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#commitAsync after executing prepareAsync(); We bind listener on prepare future. Perhaps its better initially bind listener and then execute

optimistic transaction caching

Hi all ! Optimistic transaction of READ_COMMITTED mode is never cached in transaction, as it stated in documenattion. I cannot find the point in code where it is checked. -- *Best Regards,* *Kuznetsov Aleksey*

strange cacheEntry field

Hi all! There is a field rdrs in class GridDhtCacheEntry. Why do we need it ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: prepare phase messages handlers question

led on node2, > not on node1. > > 2017-03-22 20:26 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > correct me if im wrong. Consider node1 called cache.put(key1, val1); > > So node1 creates cacheEntry1. If Affinity function decides node2 holds > key1 >

strange GridCacheReturn

Hi all! what is the use of GridCacheReturn ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: strange cacheEntry field

ted as well alongside with backup nodes. > > See GridCacheContext#dhtMap(UUID, AffinityTopologyVersion, > GridDhtCacheEntry, GridCacheVersion, IgniteLogger, > Map<ClusterNode,List>, > Map<ClusterNode,List>) > > --AG > > 2017-03-22 18:03 GMT+03:00 ALEKSEY KUZNETSOV <

Re: prepare phase messages handlers question

messages are part of 2-phase commit protocol. > They are sent from a primary node to backup nodes. > > > On Mon, Mar 20, 2017 at 7:41 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > Hi all! > > What is the point of sending GridDhtTxPr

remap response during prepare phase

Hi, igniters! My questions is the following. what is "remap response" GridNearTxPrepareResponse in processNearTxPrepareRequest? -- *Best Regards,* *Kuznetsov Aleksey*

Re: distributed transaction of non-single coordinator

пт, 17 мар. 2017 г. в 19:26, Sergi Vladykin <sergi.vlady...@gmail.com>: > You know better, go ahead! :) > > Sergi > > 2017-03-17 16:16 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > we've discovered several problems regarding your "accumula

question about peeking entry from cache

Hi all! There is method that peek cache entry from a cache org.apache.ignite.internal.processors.cache.GridCacheAdapter#peekEx(java.lang.Object) And there is another method: org.apache.ignite.internal.processors.cache.GridCacheMapEntry#peek(boolean, boolean, boolean,

Re: putting entity into cache while commiting.Why!?

return null; > } > }); > > Transaction tx = > transactions.txStart(TransactionConcurrency.OPTIMISTIC, > TransactionIsolation.READ_COMMITTED); > assertNull(cache.get("key1")); // <- This check passes > tx.commit(); > > > 2017-03-30

Re: distributed transaction of non-single coordinator

So, what do u think on my idea ? ср, 29 мар. 2017 г. в 10:35, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Hi! No, i dont have ticket for this. > In the ticket i have implemented methods that change transaction status to > STOP, thus letting it to commit transaction in

Re: putting entity into cache while commiting.Why!?

Alexander Fedotov <alexander.fedot...@gmail.com >: Hello Aleksey, No, the enlisted entry won't be visible for other transactions. Dirty reads are not allowed in Ignite. Kind regards, Alex 29 марта 2017 г. 7:36 PM пользователь "ALEKSEY KUZNETSOV" < alkuznetsov...@gmail.com> написа

Re: putting entity into cache while commiting.Why!?

; } } чт, 30 мар. 2017 г. в 11:55, Alexey Goncharuk <alexey.goncha...@gmail.com>: > Can you please paste the full example? > > 2017-03-30 11:50 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > But i managed to read dirty. That is my example :

Re: putting entity into cache while commiting.Why!?

; Aleksey, > > It looks like in your test the result of method atomicityMode() is not used > because you do getOrCreateCache() without the configuration argument, which > will create a cache with a default configuration, which is ATOMIC. > > 2017-03-30 12:06 GMT+03:00 ALEKSEY KUZNETSO

Re: putting entity into cache while commiting.Why!?

gt; will not throw an exception. Note that it will hang because doInTrasaction > starts a pessimistic transaction which acquires a lock on key1, and then > you put it to infinite sleep. The lock prevents the transaction from > the main thread to commit. > > 2017-03-30 15:44 GMT+03:00 ALEKSEY KUZ

Re: distributed transaction of non-single coordinator

re making these > changes and how they are supposed to work. > > --AG > > 2017-03-30 10:43 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > So, what do u think on my idea ? > > > > ср, 29 мар. 2017 г. в 10:35, ALEKSEY KUZNETSOV <alkuznetsov...@gmai

usimg of other JTA implementation

Igniters! Why havent u made use of some open JTA implementation for distributed transactions instead of implementing own one -- *Best Regards,* *Kuznetsov Aleksey*

Re: prepare phase messages handlers question

gt; 2017-03-22 18:37 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > When optimistic transaction occures, there is a lock on entities - > > org.apache.ignite.internal.processors.cache.transactions. > > IgniteTxManager#lockMultiple > > Don't you know, wh

cache entry invalidating

hi all ! why do we need to invalidate cache entry in org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareRequest#invalidateNearEntry(int, boolean) -- *Best Regards,* *Kuznetsov Aleksey*

putting entity into cache while commiting.Why!?

Hello, Igniters! I have one more question to you. Will appreciate any help. Consider cache with near , dht configured not null. When we start commit transaction , in method *org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#enlistWriteEntry* we put newly created entry

Re: distributed transaction of non-single coordinator

ctly was > done and how the things work. > > — > Denis > > > On Mar 28, 2017, at 8:32 AM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > > > Hi, Igniters! I 've made implementation of transactions of non-single > > coordinator. Here you can start

serializable tx prepare future

Hi all ! In GridNearTxLocal while preparing phase in optimistic mode : *org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#prepareNearTxLocal* we check serializable() and create GridNearOptimisticSerializableTxPrepareFuture What is the point of serializable future ? --

Re: distributed transaction of non-single coordinator

le bit about it. > > 2017-03-31 9:53 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > so what do u think on the issue ? > > > > чт, 30 Мар 2017 г., 17:49 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > > > Hi ! Thanks for help. I've c

NearCache transaction qeustion

Hi all! Consider we have 4 nodes. Node1 contains key1, Node2 contains key1 backup, and Node3 near-contains (contains in near cache) key1. Now we commit key1 value change like the following : Node4Cache.put(key1, updatedValue); >From my point of view Node1 receives prepare request and send

Re: distributed transaction of non-single coordinator

only then, when > we understand all implications, we should move to development stage. > > On Wed, Mar 15, 2017 at 10:38 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com> wrote: > > > Right > > > > ср, 15 мар. 2017 г. в 10:35, Sergi Vladykin <sergi.vlady.

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Its not simple as you say) Im confused with numerous sender\listener etc. methods. It looks like, coordinator node sends DynamicCacheChangeBatch message, with cache create request over cacheProcessor to smbd. But i cannot trace cache startup flow from this point. чт, 9 мар. 2017 г. в 17:46, Yakov

Re: distributed transaction of non-single coordinator

just rollbacks and signals > to Orchestrator to restart the job with new `otx` > > PROFIT!! > > This approach even allows you to run independent parts of the graph in > parallel (with TX transfer you will always run only one at a time). Also it > does not require inventi

Re: distributed transaction of non-single coordinator

ady...@gmail.com>: > What is Orchestrator for you? Is it a thing from Microsoft or your custom > in-house software? > > Sergi > > 2017-03-14 18:00 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > Fine. Let's say we've got multiple servers which

Re: distributed transaction of non-single coordinator

updated keys, but also versions of any other keys end > result depends on. > > After that Committer Service has to do a cleanup (may be outside of the > committing tx) to come to the following final state: > > [k1 => v1a] > [k2 => v2ab] >

Re: Unused argument in DirectMessageWriter

watch him, he is gonna remove all the messages he doesn't like :) чт, 16 мар. 2017 г. в 14:56, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Hi, > > These classes are part of plugin framework. Even though 'name' argument is > not used by Ignite implementations, it can be used by

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

It still unclear , how could i notify coordinator that cache creation failed чт, 9 мар. 2017 г. в 17:46, Yakov Zhdanov : Alexey, you should understand how caches startup and partition map exchange work. I would suggest you start couple of nodes in single VM and simply do

prepare phase messages handlers question

Hi all! What is the point of sending GridDhtTxPrepareRequest and GridDhtTxPrepareResponse messages? What is the logic behind processDhtTxFinishRequest and processDhtTxPrepareResponse ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: transactions classes usage

> If originating node is primary the same time, then only GridDhtTx*Request > is sent. > > > On Fri, Mar 17, 2017 at 4:48 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > Hi all! We've got a group of GridDhtTx*Request classes, how do they > re

Re: distributed transaction of non-single coordinator

bly. > > Sergi > > 2017-03-16 15:54 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > hmm, If we have millions of entities, and millions of operations, would > not > > this approache lead to memory overflow and perfomance degradation > > > >

Re: distributed transaction of non-single coordinator

the Ignite > transactions inside of all Services must be optimistic here to be able to > read this locked key. > > But again I do not recommend you using this approach until you have a > reliable deadlock avoidance scheme. > > Sergi > > > > > > > > 2017-03

transactions classes usage

Hi all! We've got a group of GridDhtTx*Request classes, how do they relate to GridNearTx*Request classes? -- *Best Regards,* *Kuznetsov Aleksey*

Re: distributed transaction of non-single coordinator

gt; Sergi > > 2017-03-14 22:46 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > orchestrator is a custom thing. He is responsible for managing business > > scenarios flows. Many nodes are involved in scenarios. They exchange data > > and folow

Re: distributed transaction of non-single coordinator

some Service A introduce changes? So no other service is allowed to change this key-value?(sort of pessimistic blocking) May be you know some implementations of such approach ? ср, 15 мар. 2017 г. в 17:54, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Thank you very much for

Re: one point optimisation

t; As far as I know a partition is always allocated to a specific node and > does not span nodes. Ignite has default 1024 partitions on start that are > split equally across nodes. > > > On 3 Apr 2017, at 08:10, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: >

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

at the java doc about how to TouchedExpiryPolicy should be work[1]. > > [1]: > > http://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/expiry/TouchedExpiryPolicy.html > > On Mon, Apr 10, 2017 at 5:48 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > &g

Support for starting transaction in another thread

Hi, Igniters! This is a subtask for "distributed transaction of non-single coordinator" task. Will appreciate your thoughts on it. ticket : https://issues.apache.org/jira/browse/IGNITE-4887 and a commit : https://github.com/voipp/ignite/commit/aa3487bd9c203394f534c605f84e06436b638e5c -- *Best

Re: one point optimisation

any thoughts on one phase commit realization ? пн, 3 апр. 2017 г. в 19:35, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > I've attached test that prints messages exchange . Which shows us that > there are more messages then you declared in article. Perhaps, > implementation h

Re: one point optimisation

org>: > Aleksey, > > The blog describes the 1-phase commit at a high level, but I am still > curious about the differences you found. Can you share them here? > > D. > > On Mon, Apr 3, 2017 at 2:11 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com> > wrote: > > &

readyNearLocks()! wat?

Igniters! What is the purpose of calling GridNearTxLocal#readyNearLocks() After we received prepare response at primary node ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: distributed transaction of non-single coordinator

so what do u think on my idea? пт, 31 Мар 2017 г., 11:05 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > sorry for misleading you. We planned to support multi-node transactions, > but failed. > > пт, 31 мар. 2017 г. в 10:51, Alexey Goncharuk <alexey.goncha...@gmail.c

Re: one point optimisation

in ur blog u texted belonging to the same partition is nessesary for 1 phase commit. But its not guarantee belonging to the same node. Partition may span many nodes вс, 2 Апр 2017 г., 13:46 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > thank u ! > > пт, 31 Мар 2017 г., 21:06 D

Re: one point optimisation

t; > > — > Denis > > > On Mar 31, 2017, at 12:27 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > > On Fri, Mar 31, 2017 at 9:25 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > >> wrote: > > > >> Igniters! What is the point of one phase optimisation? > >> > > > > Performance > > -- *Best Regards,* *Kuznetsov Aleksey*

Re: distributed transaction of non-single coordinator

so what do u think on the issue ? чт, 30 Мар 2017 г., 17:49 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Hi ! Thanks for help. I've created ticket : > https://issues.apache.org/jira/browse/IGNITE-4887 > and a commit : > https://github.com/v

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

I have already attached simlified version. Shall i simplify it more ? вт, 11 апр. 2017 г. в 19:28, Denis Magda <dma...@apache.org>: > Can you attach the simplified version? Just want to avoid any side effects. > > — > Denis > > > On Apr 11, 2017, at 9:14 AM, ALE

incorrect work of IgniteLogger

Igniters! Suppose we have log4j-test.xml as following: ... ... Why damn IgniteLogger doesn't write info logs from TxOptimisticDeadlockDetectionTest class ?!? -- *Best Regards,*

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

So what do u think about the issue ? ср, 12 апр. 2017 г. в 10:42, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > I have already attached simlified version. Shall i simplify it more ? > > вт, 11 апр. 2017 г. в 19:28, Denis Magda <dma...@apache.org>: > > Can you at

  1   2   3   >