ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Budnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9888) Document MVCC continuous queries
Date Thu, 01 Nov 2018 15:20:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671738#comment-16671738
] 

Artem Budnikov commented on IGNITE-9888:
----------------------------------------

[~pgarg] 

Please review [https://apacheignite.readme.io/v2.6/docs/multiversion-concurrency-control#section-continuous-queries]

 

> Document MVCC continuous queries
> --------------------------------
>
>                 Key: IGNITE-9888
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9888
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>            Reporter: Vladimir Ozerov
>            Assignee: Artem Budnikov
>            Priority: Major
>             Fix For: 2.7
>
>
> Key differences with continuous queries for non-MVCC caches:
> 1) When event is received, subsequent read of the same key may still return previous
value for some time (i.e. no guarantee of happens-before between event and subsequent read)
> 2) Keys for notification are kept in memory. If transaction is too large, OOME could
happen. In order to avoid that, we skip notification of too large transactions.
> [~rkondakov], could you please elaborate on how is this implemented?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message