You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Veselovsky (JIRA)" <ji...@apache.org> on 2015/11/11 16:51:10 UTC
[jira] [Comment Edited] (IGNITE-1566) Hadoop: In case if IGFS name
is missing in the URI, the connection failure message should be more
informative.
[ https://issues.apache.org/jira/browse/IGNITE-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999081#comment-14999081 ]
Ivan Veselovsky edited comment on IGNITE-1566 at 11/11/15 3:50 PM:
-------------------------------------------------------------------
Relaxed slightly the logic of authority checking: if the URI authority does not containg IGFS name or Grid name, external (not embedded) connection is successful -- the IGFS owning this port is connected to. This is possible and is not contradictory because only one IGFS instance can be bound to a certain port.
was (Author: iveselovskiy):
Relaxed slightly the logic of authority checking: if the URI authority does not containg IGFS name or Grid name, connection is successful. This is possible and is not contradictory because only one IGFS instance can be bound to a certain port.
> Hadoop: In case if IGFS name is missing in the URI, the connection failure message should be more informative.
> --------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-1566
> URL: https://issues.apache.org/jira/browse/IGNITE-1566
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
> Affects Versions: ignite-1.4
> Reporter: Ivan Veselovsky
> Assignee: Vladimir Ozerov
>
> User has IGFS "igfs" configured in Ignite node.
> After that he tries to connect to it with hadoop client using command
> {code}
> $ hadoop fs -ls igfs://127.0.0.1:10500/
> {code}
> And gets the following error message:
> {code}ls: Failed to communicate with IGFS.{code} .
> The problem is that IGFS name is missing in the URI. But the error message does not give any hint about that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)