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-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
Date Wed, 03 Aug 2016 12:47:21 GMT

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

Vladimir Ozerov commented on IGNITE-3331:
-----------------------------------------

Key methods:
{{IgfsMetaManager.runClientTask}}
{{IgfsMetaManager.clientCompute}}
{{FileSystemConfiguration.isColocateMetadata}}

If colocate metadata flag is set, we should pick only primary node for IgfsUtils.ROOT_ID key
in meta cache. Probably this can be achieved with {{IgniteCompute.affinityCall}} method.

> IGFS: Route client tasks to primary node when metadata co-location is enabled.
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-3331
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3331
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Priority: Critical
>              Labels: important, performance
>             Fix For: 1.8
>
>
> Currently we route IGFS client tasks to random metadata data node. When co-location is
enabled, it makes sense to requests which are going to change metadata directly to primary
node. 



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

Mime
View raw message