You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2019/01/24 15:24:00 UTC
[jira] [Resolved] (IGNITE-11007) MVCC: Potential NPE on
non-affinity node for mvcc cache.
[ https://issues.apache.org/jira/browse/IGNITE-11007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Seliverstov resolved IGNITE-11007.
---------------------------------------
Resolution: Not A Problem
Actually TxLog creates on each data node regardless the node is affinity node or not. So, the exception cannot be thrown.
> MVCC: Potential NPE on non-affinity node for mvcc cache.
> --------------------------------------------------------
>
> Key: IGNITE-11007
> URL: https://issues.apache.org/jira/browse/IGNITE-11007
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Andrew Mashenkov
> Assignee: Igor Seliverstov
> Priority: Major
>
> It is possible, non-affinity node (mvcc coordinator or near node) for any mvcc cache can try to track tx states and update txLog.
> However, txLog may not exists on node if node isn't data node for any mvcc cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)