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] [Comment Edited] (IGNITE-3405) IGFS: Do not allow DUAL -> PRIMARY -> DUAL modes interleaving.
Date Fri, 01 Jul 2016 18:33:11 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359303#comment-15359303
] 

Ivan Veselovsky edited comment on IGNITE-3405 at 7/1/16 6:32 PM:
-----------------------------------------------------------------

https://github.com/apache/ignite/pull/845


was (Author: iveselovskiy):
https://github.com/apache/ignite/pull/845

wrt 3) : I did not see how we can effectively  reduce this method implementation or usages.

> IGFS: Do not allow DUAL -> PRIMARY -> DUAL modes interleaving.
> --------------------------------------------------------------
>
>                 Key: IGNITE-3405
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3405
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.7
>
>
> Currently we allow almost any combinations of path modes. This appears to be wrong. Consider
the following scenario:
> 1) /dir1 -> PRIMARY
> 2) /dir1/dir2 -> DUAL
> It is impossible to support this scenario properly because {{dir1}} will be created in
both file systems anyway, but primary and secondary representation will be "detached" from
each other.
> Instead, we should allow only DUAL -> PRIMARY and DUAL -> PROXY transitions. Any
other combinations doesn't make sense.



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

Mime
View raw message