Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 7 Jul 2017 19:21:00 +0000 (UTC)
From: "James Clampffer (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13085576.1499455248000.196306.1499455260107@Atlassian.JIRA>
In-Reply-To: <JIRA.13085576.1499455248000@Atlassian.JIRA>
References: <JIRA.13085576.1499455248000@Atlassian.JIRA> <JIRA.13085576.1499455248565@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-12103) libhdfs++: Provide workaround to
 support cancel on filesystem connect until HDFS-11437 is resolved
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 07 Jul 2017 19:21:04 -0000

James Clampffer created HDFS-12103:
--------------------------------------

             Summary: libhdfs++: Provide workaround to support cancel on filesystem connect until HDFS-11437 is resolved
                 Key: HDFS-12103
                 URL: https://issues.apache.org/jira/browse/HDFS-12103
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: James Clampffer
            Assignee: James Clampffer


HDFS-11437 is going to take a non-trivial amount of work to do right.  In the meantime it'd be nice to have a way to cancel pending connections (even when the FS claimed they are finished).  

Proposed workaround is to relax the rules about when FileSystem::CancelPending connect can be called since it isn't able to properly determine when it's connected anyway.  In order to determine when the FS has connected you can do some simple RPC call since that will wait on failover.  If CancelPending can be called during that first RPC call then it will effectively be canceling FileSystem::Connect

Current cancel rules - asterisk on steps where CancelPending is allowed

FileSystem::Connect called
FileSystem communicates with first NN *
FileSystem::Connect returns - even if it hasn't communicated with the active NN

Proposed relaxation
FileSystem::Connect called
FileSystem communicates with first NN*
FileSystem::Connect returns *
FileSystem::GetFileInfo called * -any namenode RPC call will do, ignore perm errors
RPC engine blocks until it hits the active or runs out of retries *
FileSystem::GetFileInfo returns

It'd be up to the user to add in the dummy NN RPC call.  Once HDFS-11437 is fixed this workaround can be removed.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org