ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Veselovsky (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1298) Data and Meta in IGFS should be updated in one transaction.
Date Wed, 26 Aug 2015 09:38:45 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ivan Veselovsky updated IGNITE-1298:
------------------------------------
    Description: 
Tests written to check behavior IGNITE-1277 revealed problems on file data writing when some
nodes have left the topology (see tests added in IGNITE-1277). 
In particular, meta data and file data are processed in separate transactions. So, one can
complete while another may not. To fix that we need to link them together in one transaction.

  was:
Tests written to check behavior IGNITE-1277 revealed problems on file data writing when some
nodes have left the topology (see tests added in IGNITE-1277). Presumably this is because
of 2 issues: 
1) meta data and file data are processed in separate transactions. So, one can complete while
another may not. To fix that we need to link them together in one transaction.
2) IGFS files may not be unlocked. (see IGNITE-1299)


> Data and Meta in IGFS should be updated in one transaction.
> -----------------------------------------------------------
>
>                 Key: IGNITE-1298
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1298
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Ivan Veselovsky
>            Assignee: Ivan Veselovsky
>             Fix For: ignite-1.4
>
>
> Tests written to check behavior IGNITE-1277 revealed problems on file data writing when
some nodes have left the topology (see tests added in IGNITE-1277). 
> In particular, meta data and file data are processed in separate transactions. So, one
can complete while another may not. To fix that we need to link them together in one transaction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message