[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7371: Fix Version/s: (was: 2.8) > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Critical > Labels: mvcc_performance > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7371: Issue Type: Task (was: New Feature) > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Critical > Labels: mvcc_performance > Fix For: 2.8 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7371: Labels: mvcc_performance (was: ) > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Critical > Labels: mvcc_performance > Fix For: 2.8 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7371: Priority: Critical (was: Major) > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Critical > Fix For: 2.8 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7371: Fix Version/s: (was: 2.7) 2.8 > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Fix For: 2.8 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7371: Fix Version/s: (was: 2.8) 2.7 > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7371: Fix Version/s: (was: 2.7) 2.8 > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Fix For: 2.8 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-7371: - Description: Repeatable read isolation implies that each GET operation whithin tx gets a last commited version of entry *at the time the tx was started*. A value that just has been got, should be cached locally in TX to avoid remote call on repeatable get(). was: Repeatable read isolation implies that each GET operation whithin tx gets a last commited version of entry *at the time the tx was started*. -Curentrly we get a last commited version of entry *at the time the first read operation invokes on a particular key whithin tx.* We need to fix this unconsistence.- A value that just has been got, should be cached locally. > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > A value that just has been got, should be cached locally in TX to avoid > remote call on repeatable get(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7371) MVCC: Repeatable read TX should cache entries locally.
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-7371: - Summary: MVCC: Repeatable read TX should cache entries locally. (was: MVCC TX Repeatable read semantic) > MVCC: Repeatable read TX should cache entries locally. > -- > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. > -Curentrly we get a last commited version of entry *at the time the first > read operation invokes on a particular key whithin tx.* We need to fix this > unconsistence.- > A value that just has been got, should be cached locally. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
