ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3405) IGFS: Do not allow DUAL -> PRIMARY -> DUAL modes interleaving.
Date Thu, 30 Jun 2016 11:33:10 GMT

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

Vladimir Ozerov commented on IGNITE-3405:
-----------------------------------------

Implementation notes:
1) Paths must be validated on start. Corresponding tests must be added.
2) Review {{IgfsImpl.checkConflictWithPrimary()}} - probably this method should go away.
3) Review {{IgfsModeResolver.resolveChildrenModes()}} usages inside IgfsImpl. Probably we
will not need it anymore.

> 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: Ivan Veselovsky
>            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