ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Pavlukhin <vololo...@gmail.com>
Subject Re: Data consistency essentials explained
Date Thu, 28 Nov 2019 06:25:02 GMT
Alexei,

Many thanks for that article! Really nice that now we have a document
describing Ignite approach for data consistency. I think it is super
important because it is not trivial and very Ignite specific. I
believe lots of Ignite developers will learn something new from this
document.

By the way, I noticed a link to GridGain documentation [1]. Is it fine?

[1] https://www.gridgain.com/docs/latest/developers-guide/key-value-api/transactions#pessimistic-transactions

чт, 28 нояб. 2019 г. в 02:49, Denis Magda <dmagda@apache.org>:
>
> Alex,
>
> Thanks a lot for putting your knowledge on paper. That's an invaluable contribution!
>
> Looping in the user community (will be interesting for those who use native persistence)
and has just spread the word via Ignite twitter handle:
> https://twitter.com/ApacheIgnite/status/1199837055007612928
>
> -
> Denis
>
>
> On Wed, Nov 27, 2019 at 12:29 AM Alexei Scherbakov <alexey.scherbakoff@gmail.com>
wrote:
>>
>> Igniters,
>>
>> As a final action in my almost year long effort in repairing data
>> consistency related issues for transactional persistent caches I've
>> prepared an article explaining the principles of achieving the consistency
>> between partition copies for these scenarios [1]
>> Comments and suggestions are welcome.
>> I plan to keep the article in actual state if something will change in this
>> area in the future.
>> Fixes were mostly done under IGNITE-10780 and several follow-up fixes.
>>
>> There is still work to be done. Currently I'm working on similar issue for
>> atomic persistent caches [2]. I hope to give an update on that soon.
>>
>> [1]  https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
>> [2] https://issues.apache.org/jira/browse/IGNITE-11797
>> --
>>
>> Best regards,
>> Alexei Scherbakov



-- 
Best regards,
Ivan Pavlukhin

Mime
View raw message