[
https://issues.apache.org/jira/browse/IGNITE-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10738:
------------------------------------
Description:
Currently MVCC caches are not allowed to be located in data regions with
enabled page evictions in in-memory mode because unexpected data purges may
lead to repeatable read semantics violations. See this
[thread|http://apache-ignite-developers.2346864.n4.nabble.com/Page-eviction-for-in-memory-mode-with-enabled-MVCC-tt39460.html]
on dev-list for details.
We need to think about a suitable solution to this problem and implement it.
See branch professional/ignite-10448-proto for prototype.
was:
Currently MVCC caches are not allowed to be located in data regions with
enabled page evictions in in-memory mode because unexpected data purges may
lead to repeatable read semantics violations. See this
[thread|http://apache-ignite-developers.2346864.n4.nabble.com/Page-eviction-for-in-memory-mode-with-enabled-MVCC-tt39460.html]
on dev-list for details.
We need to think about a suitable solution to this problem and implement it.
> MVCC: Enable page evictions for MVCC caches with in-memory mode
> ---------------------------------------------------------------
>
> Key: IGNITE-10738
> URL: https://issues.apache.org/jira/browse/IGNITE-10738
> Project: Ignite
> Issue Type: Improvement
> Components: mvcc
> Reporter: Roman Kondakov
> Priority: Major
>
> Currently MVCC caches are not allowed to be located in data regions with
> enabled page evictions in in-memory mode because unexpected data purges may
> lead to repeatable read semantics violations. See this
> [thread|http://apache-ignite-developers.2346864.n4.nabble.com/Page-eviction-for-in-memory-mode-with-enabled-MVCC-tt39460.html]
> on dev-list for details.
> We need to think about a suitable solution to this problem and implement it.
> See branch professional/ignite-10448-proto for prototype.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
