ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (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 14:45:20 GMT

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

Mime
View raw message