[jira] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Labels: important performance (was: important perfomance) > 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)
[jira] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Fix Version/s: (was: 1.7) 1.8 > 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, perfomance > 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] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Assignee: (was: Vladimir Ozerov) > 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, perfomance > Fix For: 1.7 > > > 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] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Issue Type: Sub-task (was: Task) Parent: IGNITE-3552 > 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: Vladimir Ozerov >Priority: Critical > Labels: important, perfomance > Fix For: 1.7 > > > 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] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Labels: important perfomance (was: perfomance) > 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: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Labels: important, perfomance > Fix For: 1.7 > > > 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] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Issue Type: Task (was: Sub-task) Parent: (was: IGNITE-3245) > 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: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Labels: important, perfomance > Fix For: 1.7 > > > 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] [Updated] (IGNITE-3331) IGFS: Route client tasks to primary node when metadata co-location is enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3331: Issue Type: Sub-task (was: Bug) Parent: IGNITE-3245 > 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: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > > 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)