You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/04/06 16:50:12 UTC
[jira] [Updated] (IGNITE-462) Revise the logic of IGFS
communication start
[ https://issues.apache.org/jira/browse/IGNITE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-462:
-----------------------------------
Fix Version/s: (was: sprint-3)
sprint-4
> Revise the logic of IGFS communication start
> --------------------------------------------
>
> Key: IGNITE-462
> URL: https://issues.apache.org/jira/browse/IGNITE-462
> Project: Ignite
> Issue Type: Task
> Components: hadoop
> Affects Versions: sprint-2
> Reporter: Ivan Veselovsky
> Assignee: Ivan Veselovsky
> Priority: Minor
> Fix For: sprint-4
>
>
> See IGNITE-419.
> Issues to be addressed:
> 1) Is that okay that the client tries several communication protocols in turn each time it initiates IGFS communication? (There is no way to specify communication protocol on the client side).
> 2) Second handshake is performed upon filesystem closing because the instance is not cached, so each client FS command involves 2 handshakes. May be this is just a bug -- need to investigate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)