[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3331:


Github user asfgit closed the pull request at:

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


> 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
>Assignee: Taras Ledkov
>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)

[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3331:
-

Slight performance gain is confirmed.

> 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
>Assignee: Taras Ledkov
>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)

[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3331:
-

Patch looks good for me. Need to test it's perf.

> 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
>Assignee: Taras Ledkov
>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)

[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3331:
--

[Tests 
results|http://149.202.210.143:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F921%2Fhead]

> 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
>Assignee: Taras Ledkov
>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)

[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3331:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3331 IGFS: Route client tasks to primary node when metadata co…

…-location is enabled.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3331

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/921.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #921


commit be6ad25e2107267928122cda93dfa28a0da2166d
Author: tledkov-gridgain 
Date:   2016-08-03T13:47:06Z

IGNITE-3331 IGFS: Route client tasks to primary node when metadata 
co-location is enabled.




> 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
>Assignee: Taras Ledkov
>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)

[jira] [Commented] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)