[
https://issues.apache.org/jira/browse/IGNITE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747891#comment-16747891
]
Igor Seliverstov commented on IGNITE-10757:
-------------------------------------------
I'd like to extract TxLog related logic into a separate manager too.
> 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)
