ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Veselovsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-462) Revise the logic of IGFS communication start
Date Wed, 18 Nov 2015 13:17:11 GMT

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

Ivan Veselovsky commented on IGNITE-462:
----------------------------------------

Item "2)" (Second handshake is performed upon filesystem closing) is not valid any more after
some recent changes -- now only one connection is performed per one successful operation.

> 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: 1.5
>
>
> 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)

Mime
View raw message