ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Zinoviev (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-11871) [ML] IP resolver in TensorFlow cluster manager doesn't work properly
Date Tue, 19 Nov 2019 10:46:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexey Zinoviev reassigned IGNITE-11871:
----------------------------------------

    Assignee: Alexey Zinoviev  (was: Anton Dmitriev)

> [ML] IP resolver in TensorFlow cluster manager doesn't work properly
> --------------------------------------------------------------------
>
>                 Key: IGNITE-11871
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11871
>             Project: Ignite
>          Issue Type: Bug
>          Components: ml
>    Affects Versions: 2.7
>            Reporter: Anton Dmitriev
>            Assignee: Alexey Zinoviev
>            Priority: Major
>
> TensorFlow cluster manager requires NodeId to be resolved into IP address or hostname
to pass the address/name to TensorFlow worker. Currently, it uses strategy "return first"
and returns the first available address/name. As a result of that, in the case when the server
has more than one interface cluster resolver might work incorrectly and return different addresses/names
for the same server.
> To fix this problem we need to update [TensorFlowServerAddressSpec|https://github.com/apache/ignite/blob/master/modules/tensorflow/src/main/java/org/apache/ignite/tensorflow/cluster/spec/TensorFlowServerAddressSpec.java]
so that it returns the same address/name for the same server all the time. If a server has
multiple network interfaces we need to find a "GCD", a network with all Ignite nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message