Return-Path: 
 <dev-return-2968-apmail-ignite-dev-archive=ignite.apache.org@ignite.incubator.apache.org>
X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org
Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 048A31036A
	for <apmail-ignite-dev-archive@minotaur.apache.org>;
 Wed, 11 Mar 2015 09:30:00 +0000 (UTC)
Received: (qmail 92413 invoked by uid 500); 11 Mar 2015 09:29:59 -0000
Delivered-To: apmail-ignite-dev-archive@ignite.apache.org
Received: (qmail 92371 invoked by uid 500); 11 Mar 2015 09:29:59 -0000
Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ignite.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ignite.incubator.apache.org>
List-Post: <mailto:dev@ignite.incubator.apache.org>
List-Id: <dev.ignite.incubator.apache.org>
Reply-To: dev@ignite.incubator.apache.org
Delivered-To: mailing list dev@ignite.incubator.apache.org
Received: (qmail 92360 invoked by uid 99); 11 Mar 2015 09:29:59 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Mar 2015 09:29:59 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 11 Mar 2015 09:29:58 +0000
Received: (qmail 92029 invoked by uid 99); 11 Mar 2015 09:29:38 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Mar 2015 09:29:38 +0000
Date: Wed, 11 Mar 2015 09:29:38 +0000 (UTC)
From: "Ivan Veselovsky (JIRA)" <jira@apache.org>
To: dev@ignite.incubator.apache.org
Message-ID: <JIRA.12779854.1425579198000.61774.1426066178401@Atlassian.JIRA>
In-Reply-To: <JIRA.12779854.1425579198000@Atlassian.JIRA>
References: <JIRA.12779854.1425579198000@Atlassian.JIRA>
 <JIRA.12779854.1425579198942@arcas>
Subject: [jira] [Comment Edited] (IGNITE-419) Each IGFS operation causes two
 "Handshake failed" warnings to appear
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Ivan Veselovsky edited comment on IGNITE-419 at 3/11/15 9:28 AM:
-----------------------------------------------------------------

IGFS communication protocol configured on server only. Client knows host and port number, but does not know the protocol of the communication. It tries each protocol (embedded, shmem, local TCP, remote TCP, in this order) until first success.
The warnings appear because TCP protocol is configured to communicate with IGFS (default), and on Unix systems the client first tries to connect using shmem and fails. After that it tries again with TCP and succeeds.
Adding the following property to Ignite config solves the problem:
{code}
    <property>
        <name>fs.igfs.igfs@localhost.endpoint.no_local_shmem</name>
        <value>true</value>
    </property>
{code}

Two warnings appear because due to disabled filesystem instance caching upon filesystem closing the filesystem instance is created again, what, in turn, causes one more handshake (see org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem#close) .

Currently (for the Sprint-2 release) we just disabled the handshake warnings on server side.
IGNITE-462 created to clarify those issues. 


was (Author: iveselovskiy):
IGFS communication protocol configured on server only. Client knows host and port number, but does not know the protocol of the communication. It tries each protocol (embedded, shmem, local TCP, remote TCP, in this order) until first success.
The warnings appear because TCP protocol is configured to communicate with IGFS (default), and on Unix systems the client first tries to connect using shmem and fails. After that it tries again with TCP and succeeds.
Adding the following property to Ignite config solves the problem:
{code}
    <property>
        <name>fs.igfs.igfs@localhost.endpoint.no_local_shmem</name>
        <value>true</value>
    </property>
{code}

Two warnings appear because due to disabled filesystem instance caching upon filesystem closing the filesystem instance is created again, what, in turn, causes one more handshake (see org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem#close) .

Currently (for the Sprint-2 release) we just disabled the handshake warnings on server side.


> Each IGFS operation causes two "Handshake failed" warnings to appear
> --------------------------------------------------------------------
>
>                 Key: IGNITE-419
>                 URL: https://issues.apache.org/jira/browse/IGNITE-419
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: sprint-1
>            Reporter: Ivan Veselovsky
>            Assignee: Vladimir Ozerov
>            Priority: Minor
>             Fix For: sprint-2
>
>         Attachments: IGNITE-419--a.patch
>
>
> Pre-condition: Hadoop client configured to work with igfs:// (does not matter this is pure IGFS or a layer upon HDFS).
> In Hadoop client do any fs-related operation, e.g.
> ./hadoop fs -touchz /foo
> Observe in Ignite console the following 2 lines:
> [21:07:10,947][WARN ][igfs-client-worker-69-#192%null%][GridWorker] Handshake failed.
> [21:07:11,658][WARN ][igfs-client-worker-71-#194%null%][GridWorker] Handshake failed.
> However, in most cases no functionality appears to be broken.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)