You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/08/20 11:36:00 UTC
[jira] [Commented] (IGNITE-7966) MVCC TX Review cache/Ignite
configuration for MVCC needs
[ https://issues.apache.org/jira/browse/IGNITE-7966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585818#comment-16585818 ]
Vladimir Ozerov commented on IGNITE-7966:
-----------------------------------------
Considerations:
# Introduce new {{CacheAtomicityMode.TRANSACTIONAL_MVCC}}
# Do not allow to change cache this mode during restart (when persistence is enabled)
# Do not allow transactions between {{TRANSACTIONAL}} and {{TRANSACTIONAL_MVCC}} caches
# Add limitation to cache group - all caches within a group should have the same mode
> MVCC TX Review cache/Ignite configuration for MVCC needs
> --------------------------------------------------------
>
> Key: IGNITE-7966
> URL: https://issues.apache.org/jira/browse/IGNITE-7966
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc, sql
> Reporter: Igor Seliverstov
> Priority: Major
>
> We need to rethink Ignite and Cache configuration to have a control on such parameters as VACUUM frequency, TxLog data-region parameters, whether MVCC enabled or not for particular cache etc. Most of such parameters are hardcoded now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)