[jira] [Updated] (IGNITE-10757) Refactoring: split MvccProcessor into multiple components
[ https://issues.apache.org/jira/browse/IGNITE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10757: - Fix Version/s: (was: 2.8) > Refactoring: split MvccProcessor into multiple components > - > > Key: IGNITE-10757 > URL: https://issues.apache.org/jira/browse/IGNITE-10757 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Minor > > In current implementation MvccProcessor has multiple responsibilities which > can be extracted into separate components. Also it looks like that we do not > need an independent processor here because all logic is bound to > CacheProcessor. At least 3 components could be created: > 1. ShapshotManager responsible for granting MVCC snapshots and handling > related messages. > 2. LockManager implementing (exclusive) locking for write operations and > associated wait queues. Deadlock detection facilities could be also placed > here. > 3. VacuumManager responsible for scavenging not needed anymore row versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10757) Refactoring: split MvccProcessor into multiple components
[ https://issues.apache.org/jira/browse/IGNITE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10757: - Priority: Minor (was: Major) > Refactoring: split MvccProcessor into multiple components > - > > Key: IGNITE-10757 > URL: https://issues.apache.org/jira/browse/IGNITE-10757 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Minor > Fix For: 2.8 > > > In current implementation MvccProcessor has multiple responsibilities which > can be extracted into separate components. Also it looks like that we do not > need an independent processor here because all logic is bound to > CacheProcessor. At least 3 components could be created: > 1. ShapshotManager responsible for granting MVCC snapshots and handling > related messages. > 2. LockManager implementing (exclusive) locking for write operations and > associated wait queues. Deadlock detection facilities could be also placed > here. > 3. VacuumManager responsible for scavenging not needed anymore row versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10757) Refactoring: split MvccProcessor into multiple components
[ https://issues.apache.org/jira/browse/IGNITE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10757: - Issue Type: Task (was: Improvement) > Refactoring: split MvccProcessor into multiple components > - > > Key: IGNITE-10757 > URL: https://issues.apache.org/jira/browse/IGNITE-10757 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > In current implementation MvccProcessor has multiple responsibilities which > can be extracted into separate components. Also it looks like that we do not > need an independent processor here because all logic is bound to > CacheProcessor. At least 3 components could be created: > 1. ShapshotManager responsible for granting MVCC snapshots and handling > related messages. > 2. LockManager implementing (exclusive) locking for write operations and > associated wait queues. Deadlock detection facilities could be also placed > here. > 3. VacuumManager responsible for scavenging not needed anymore row versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10757) Refactoring: split MvccProcessor into multiple components
[ https://issues.apache.org/jira/browse/IGNITE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10757: -- Ignite Flags: (was: Docs Required) > Refactoring: split MvccProcessor into multiple components > - > > Key: IGNITE-10757 > URL: https://issues.apache.org/jira/browse/IGNITE-10757 > Project: Ignite > Issue Type: Improvement > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > In current implementation MvccProcessor has multiple responsibilities which > can be extracted into separate components. Also it looks like that we do not > need an independent processor here because all logic is bound to > CacheProcessor. At least 3 components could be created: > 1. ShapshotManager responsible for granting MVCC snapshots and handling > related messages. > 2. LockManager implementing (exclusive) locking for write operations and > associated wait queues. Deadlock detection facilities could be also placed > here. > 3. VacuumManager responsible for scavenging not needed anymore row versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
