[
https://issues.apache.org/jira/browse/IGNITE-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407283#comment-15407283
]
Vladimir Ozerov commented on IGNITE-3580:
-----------------------------------------
As this task is pretty big, I would split it into three subtasks, and implement
them one by one in that order:
1) Pass {{IgfsOperationContext}} to all relevant {{IgfsMetaManager}} methods.
2) Pass {{IgfsOperationContext}} to all relevant {{IgfsDataManager}} methods.
3) At these points neither {{IgfsMetaManager}}. nor {{IgfsDataManager}} will
depend on {{IgfsContext}}. So we can easily move them to {{IgfsProcessor}} and
ensure that they always start, even if no IGFSs are configured on the node.
> IGFS: Allow IGFS tasks execution on machines where IGFS is not configured.
> --------------------------------------------------------------------------
>
> Key: IGNITE-3580
> URL: https://issues.apache.org/jira/browse/IGNITE-3580
> Project: Ignite
> Issue Type: Task
> Components: IGFS
> Affects Versions: 1.6
> Reporter: Vladimir Ozerov
> Assignee: Taras Ledkov
> Priority: Critical
> Fix For: 1.8
>
>
> Currently user has to configure IGFS on all nodes where data and meta caches
> reside. Otherwise, he will not be able to execute metadata and data updates
> on these machines.
> This requirement is synthetic. No reason to force user doing this. Instead,
> all required tasks can be executed on data nodes without IGFS started on
> them. Need to refactor IGFS to allow this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
